MCP server
Connect TurboStarter to AI assistants with the built-in Model Context Protocol server.
For the complete documentation index, see llms.txt. Prefer markdown by appending.mdto documentation URLs or sendingAccept: text/markdown.
TurboStarter provides a public Model Context Protocol server for its documentation. It lets AI assistants search docs and read pages as markdown, so answers can stay grounded in the latest official documentation.
The server is exposed through a Streamable HTTP endpoint:
https://www.turbostarter.dev/mcpUse the hosted endpoint
You do not need to install or run anything locally. Point your MCP client to the hosted TurboStarter docs endpoint: https://www.turbostarter.dev/mcp.
What it provides
The MCP server gives AI clients direct access to TurboStarter documentation.
Search docs
Find relevant documentation pages by title, description, and URL.
Read markdown
Fetch the full markdown content for a documentation page.
Stay source-grounded
Help your assistant answer from official docs instead of guessing.
Quick start
Add TurboStarter to your MCP client
Configure your AI assistant to connect to the Streamable HTTP endpoint. Most MCP clients support either a project-level config file or a settings UI.
Create or update .cursor/mcp.json:
{
"mcpServers": {
"turbostarter": {
"url": "https://www.turbostarter.dev/mcp"
}
}
}Then enable the server in Cursor settings. Once connected, Cursor should show the available TurboStarter docs tools.
Create or update .mcp.json in your project:
{
"mcpServers": {
"turbostarter": {
"type": "http",
"url": "https://www.turbostarter.dev/mcp"
}
}
}Restart Claude Code and use /mcp to confirm the server is connected.
Create or update .vscode/mcp.json:
{
"servers": {
"turbostarter": {
"type": "http",
"url": "https://www.turbostarter.dev/mcp"
}
}
}Start the server from the MCP controls in VS Code.
Add the server to ~/.codex/config.toml:
[mcp_servers.turbostarter]
type = "http"
url = "https://www.turbostarter.dev/mcp"Restart Codex so it picks up the new server.
Ask TurboStarter-specific questions
Try prompts that need documentation context:
- Search the TurboStarter docs for billing webhooks.
- Read the TurboStarter authentication overview and summarize the setup.
- Find where TurboStarter documents AI-assisted development.
- Explain how the web app is structured using the TurboStarter docs.
Available tools
Your MCP client will see two documentation tools.
search_docs
Searches TurboStarter documentation by title, description, and URL.
{
"query": "billing webhooks",
"limit": 10
}limit is optional and defaults to 10. The server accepts values from 1 to 50.
read_doc
Reads a documentation page as markdown.
{
"url": "/docs/web/billing/webhooks.mdx"
}The url can be either the regular docs URL or the markdown URL returned by search_docs.
Troubleshooting
Make sure the URL is exactly https://www.turbostarter.dev/mcp and that your MCP client supports Streamable HTTP servers.
Restart the MCP client after editing its configuration. Some clients also require enabling the server in settings before tools appear.
Check that your network can reach https://www.turbostarter.dev/mcp over HTTPS. If your company uses a proxy or firewall, allow requests to the TurboStarter docs domain.
Ask it to use the TurboStarter docs MCP server explicitly. For example: "Use the TurboStarter docs MCP server to search for authentication setup, then explain the steps."
How is this guide?
Last updated on