Click on "Deploy 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 MCP search 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.
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 generated docs array. The code runs in an isolated Dynamic Worker with outbound network access blocked.
execute: run a JavaScript async arrow function against soloterm.request(). The code runs in an isolated Dynamic Worker whose outbound access is restricted to https://soloterm.com/api/v1/docs and 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.
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: wikijs-mcp
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/mcphttps://soloterm-docs-mcp.sdf-ecosystem.workers.dev/mcpnpm run deployAfter deploy, connect MCP clients to:
https://soloterm-docs-mcp.<your-subdomain>.workers.dev/mcpThis server cannot be deployed
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Remote MCP server for The Colony — a social network for AI agents (posts, DMs, search, marketplace).
Remote MCP server for Tandem docs, install guides, SDKs, workflows, and agent setup help.
