MCP Server
Connect your coding agent to these docs over the Model Context Protocol, so it answers from the current documentation instead of guessing.
These docs expose a Model Context Protocol server. Point your coding agent at it and it searches the live documentation while it works, instead of recalling a half-remembered API from its training data.
https://docs.rasto.co/_mcp
| Property | Value |
|---|---|
| Transport | Streamable HTTP |
| Authentication | None. The documentation is public |
| Access | Read only. It searches these docs and never calls the API |
| Data | Only these documentation pages. It cannot see your account, your keys, or your customers |
Install
claude mcp add --transport http rasto-docs https://docs.rasto.co/_mcp
Verify with claude mcp list. Add --scope project to share it with your
team through .mcp.json, or --scope user to use it in every project.
Create ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside
one project:
{
"mcpServers": {
"rasto-docs": {
"url": "https://docs.rasto.co/_mcp"
}
}
}
Then confirm the server shows as connected in Cursor's MCP settings.
From the command line:
code --add-mcp '{"name":"rasto-docs","type":"http","url":"https://docs.rasto.co/_mcp"}'
Or commit it to the workspace in .vscode/mcp.json:
{
"servers": {
"rasto-docs": {
"type": "http",
"url": "https://docs.rasto.co/_mcp"
}
}
}
Open Settings, then Connectors, then Add custom connector, and
paste https://docs.rasto.co/_mcp.
Edit ~/.codex/config.toml:
[mcp_servers.rasto-docs]
url = "https://docs.rasto.co/_mcp"
Edit ~/.gemini/settings.json:
{
"mcpServers": {
"rasto-docs": {
"httpUrl": "https://docs.rasto.co/_mcp"
}
}
}
The key is httpUrl. Gemini CLI reads url as the older SSE transport.
Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"rasto-docs": {
"serverUrl": "https://docs.rasto.co/_mcp"
}
}
}
Click Configure MCP Servers and add to cline_mcp_settings.json:
{
"mcpServers": {
"rasto-docs": {
"type": "streamableHttp",
"url": "https://docs.rasto.co/_mcp"
}
}
}
Set type explicitly. Without it, Cline falls back to the older SSE
transport.
Any client that supports remote MCP servers over Streamable HTTP connects with the URL alone and no authentication. If you are writing your own client:
POSTclient messages to the one endpoint, andGETit for the event stream.- Send
Accept: application/json, text/event-stream. - The
initializeresponse returns anMcp-Session-Idheader. Send it back on every later request.
What the server exposes
One tool, search_documentation. It runs a hybrid search, part semantic
and part keyword, over every page on this site.
| Parameter | Type | Default | Meaning |
|---|---|---|---|
query | string | required | What to search for |
limit | number | 10 | Maximum results |
semanticRatio | number | 0.75 | 1 is pure meaning-based matching, 0 is pure keyword. Lower it when you are searching for an exact field name or error code |
Results are matched sections, not whole pages. Each carries a url
for the section and a parent_url for the full page, which an agent can
fetch when it needs the surrounding context.
Prompts that use it well
Search the Rasto docs for what gates virtual account creation, then tell me
which error each gate returns and the exact fix for each.
Look up how wallet sends are authorized, then write the verify-then-sign
step in TypeScript. Do not sign anything the verifier has not rebuilt.
Naming the object or the error code gets better results than naming the
goal: endorsement_profile_required beats "my customer is not working".
For clients without MCP support, see Building with AI.
It covers llms.txt, per-page Markdown, and what to check in code an
assistant writes for this API.