SoloTerm Docs MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SoloTerm Docs MCPsearch for 'getting started' in the SoloTerm docs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SoloTerm Docs MCP
Remote MCP server for SoloTerm/Solo documentation, built on Cloudflare Workers with the Agents SDK MCP handler and a Code Mode-style tool surface.
The /mcp endpoint exposes only two JavaScript-oriented tools:
search: run a JavaScript async arrow function against the generateddocsarray. The code runs in an isolated Dynamic Worker with outbound network access blocked.execute: run a JavaScript async arrow function againstsoloterm.request(). The code runs in an isolated Dynamic Worker whose outbound access is restricted tohttps://soloterm.com/api/v1/docsand child routes.
There are no legacy docs tools or MCP resources. ?codemode=false is intentionally ignored so clients always receive the same search and execute tools.
Generated Docs
The docs snapshot is generated into src/generated/docs.ts from https://soloterm.com/api/v1/docs.
The Code Mode declarations shown in tool descriptions are generated into src/generated/code-mode-types.ts by the same generator. They define the in-sandbox docs, generatedAt, sourceBaseUrl, and soloterm.request() API.
At runtime, search uses a cached live docs snapshot. The Worker refreshes that cache hourly with a Cloudflare scheduled trigger (0 * * * *) and also refreshes on cache miss. If the live docs API is unavailable during refresh, the generated static snapshot remains as a fallback.
Coverage is verified against two live sources:
The docs API link graph starting at
https://soloterm.com/api/v1/docs.Public docs URLs listed in
https://soloterm.com/sitemap.xml.
npm run docs:verify refreshes the snapshot, crawls the live API graph, reads the sitemap, and fails unless the generated slugs exactly cover the union of both indexes.
Related MCP server: mcp-agno
Development
npm install
npm run docs:fetch
npm run docs:verify
npm run build
npm run dev
MCP_URL=http://localhost:8787 npm run test:mcpThe local MCP endpoint is served at:
http://localhost:8787/mcpLive Worker
https://soloterm-docs-mcp.sdf-ecosystem.workers.dev/mcpDeploy
npm run deployAfter deploy, connect MCP clients to:
https://soloterm-docs-mcp.<your-subdomain>.workers.dev/mcpThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kalepail/soloterm-docs-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server