tools/list
Published tools
Only Capability bindings with a published release appear. Draft or withdrawn tools stay hidden from agents.
ONLINESVR MCP
Connect Claude, Cursor, and your AI agents to published Store Capabilities over Streamable HTTP — same Gateway runtime as Console and REST. Browse Capabilities, authorize with your API Key, and call typed tools.
Copy this URL into your AI agent to connect over Streamable HTTP.
https://mcp.onlinesvr.comtools/call requires a platform API Key as Authorization: Bearer <API_KEY>. tools/list can discover published tools without a key. OAuth-style URL-only connect is not available yet.
Pick your client. Include an API Key so agents can run Capabilities, not only list them.
Paste into any client that supports remote Streamable HTTP MCP servers.
{
"mcpServers": {
"onlinesvr": {
"url": "https://mcp.onlinesvr.com",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}When connected, ask your agent to list MCP tools, then run a published Capability you have granted on the key — for example crawl a URL or extract page text for RAG.
Store Capabilities become MCP tools once an operator publishes a binding. Agents run selected tools without inventing a second execution stack.
onlinesvr/rag-web-browser
Browse and extract web pages into clean chunks for RAG agents, with citations and structured output.
onlinesvr/website-content-crawler
Crawl websites and extract text for AI models, vector databases, and RAG pipelines with Markdown cleanup.
onlinesvr/ai-agent-web-tools
Ready-made Capability tools your agents can call for search, crawl, extract, and summarize workflows.
onlinesvr/mcp-capability-router
Route agent requests to the right Store Capability via MCP with typed inputs and observability.
ONLINESVR does not use category query strings like ?tools=. Tools are selected via MCP Server Profiles and published bindings in the platform.
tools/list
Only Capability bindings with a published release appear. Draft or withdrawn tools stay hidden from agents.
tools/call
Calls submit through the same Gateway → Scheduler → Worker path as Console and REST. Long work returns a task_id.
Bearer auth
tools/call requires Authorization: Bearer <API_KEY> plus Capability grants and quota. Missing keys get HTTP 401.
task_id
Poll platform / Gateway order status for completion and artifacts — same identity that submitted the task.
Docs, Store, and API share one Capability contract with MCP.