Skip to content

Docs MCP Server

The build.io documentation is available as a Model Context Protocol (MCP) server, so your AI assistant can look up answers in these docs instead of guessing. Point any MCP client at:

https://docs.build.io/mcp

The server is public and read-only. It needs no OAuth, no API key and no build.io account, and it has no access to your apps or account. It only searches the pages on this site.

The server uses the Streamable HTTP transport. Any client that accepts a remote MCP server URL can connect.

$ claude mcp add --transport http build-io-docs https://docs.build.io/mcp

Open Settings → Connectors, choose Add custom connector, and enter https://docs.build.io/mcp as the URL. Leave the OAuth fields empty.

Add the server to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json to use it everywhere:

{
"mcpServers": {
"build-io-docs": {
"url": "https://docs.build.io/mcp"
}
}
}

Add the server to .vscode/mcp.json in your workspace:

{
"servers": {
"build-io-docs": {
"type": "http",
"url": "https://docs.build.io/mcp"
}
}
}
ToolDescription
search_build_io_documentationSearches the English and Japanese docs and returns up to five matching sections, each with its title, a link to the section, and its full text.

Once connected, ask your assistant a build.io question and it calls the tool on its own. For example:

  • How do review apps work on build.io, and how do I turn them on for my pipeline?
  • Which dyno size should I use for a Rails worker that needs 2 GB of memory?
  • I'm moving from Heroku. What changes in how I set config vars?

The search matches the words in your query against the words in the docs. It does not match by meaning. Queries that use the terms the docs use, like “review apps”, “config vars” or “dyno sizes”, return the best results. Japanese queries return sections from the Japanese docs.

To see what the server returns, open the MCP Inspector:

$ npx @modelcontextprotocol/inspector

Choose the Streamable HTTP transport, enter https://docs.build.io/mcp, click Connect, and run the tool from the Tools tab.

You can also call the tool with curl. The Accept header must list both application/json and text/event-stream, or the server rejects the request:

$ curl https://docs.build.io/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_build_io_documentation","arguments":{"query":"review apps"}}}'

If the assistant can’t find something that is in the docs, or the server stops responding, email support@build.io.