Local MCP server/Development

Octri API Docs MCP server

Local MCP server

Octri API Docs lets an agent search an API's docs, guides, changelog, and SDK snippets, and call that API's endpoints as tools. It is built from the OpenAPI spec by Octri. The provider's install link runs npx -y @octri/mcp locally with OCTRI_PROJECT_ID set; it does not document the api.octri.dev hosted URL used in earlier copy.

none (local stdio) Local install path Reviewed 2026-11-16
About

Where it fits

Developers working with an API documented by an OpenAPI spec who need docs search and endpoint calls.

  • Set OCTRI_PROJECT_ID for the target API.
  • Run npx -y @octri/mcp as a local server.
  • Search docs and call an API endpoint as a tool.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local Octri docs server

The provider's install link runs @octri/mcp locally and requires OCTRI_PROJECT_ID. The hosted api.octri.dev URL is not documented by the provider.

  1. Set the project ID

    Export OCTRI_PROJECT_ID with the Octri project whose OpenAPI spec should be indexed.

  2. Run the local server

    Start npx -y @octri/mcp and register that command as a local stdio MCP server.

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The server connects but no tools appear. Confirm the URL and transport, then restart the client.
  • The first tool call times out. Try a smaller request and check the provider's status or rate limits.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Octri API Docs repositoryhttps://github.com/octridev/octri-mcp