Skip to main content
Unblocked supports MCP, CLI commands, and a REST API. Choose based on whether the caller is a coding agent, a shell process, or an application.

​
Choose an interface

One team can use several interfaces. Developers can use MCP, CI jobs can use the CLI, and a backend service can send documents through the REST API.

​
MCP for coding agents

Unblocked MCP lets AI coding agents research code, pull requests, issues, documentation, and team discussions. Use it when your coding tool supports MCP and needs to find Unblocked context while it works.

​
Choose Remote MCP or Local MCP

Remote MCP and Local MCP provide the same tools. They differ in how your MCP client connects and authenticates.
The Remote MCP server does not require the Unblocked CLI. Your MCP client connects to https://getunblocked.com/api/mcpsse over HTTP and authenticates with OAuth or an API token.Choose Remote MCP when you cannot install a local binary, when your client supports HTTP instead of stdio, or when you want each team member to authenticate through a shared client configuration.
Select HTTP when your MCP client asks for a transport. Unblocked does not support the deprecated HTTP+SSE transport.
See Remote MCP setup.

​
CLI for scripts and CI

The Unblocked CLI exposes context-* commands that return JSON on standard output. Use it when a shell script, CI job, or custom agent workflow needs Unblocked context as data. The CLI supports broad research, source-specific search, filtered issue and pull request queries, and URL retrieval. It can authenticate through an interactive browser flow or an API token in a headless environment. Start with these guides:

Install the CLI

Authenticate

Query your workspace

​
REST API for custom integrations

The Unblocked REST API lets an application manage custom document collections and ask questions about your codebase. Use the REST API when you need to:
  • Send content from an unsupported data source to Unblocked.
  • Keep a custom collection of documents in sync.
  • Ask questions from a backend service and receive answers with references.
REST requests use a Personal Access Token or Team Access Token in the Authorization header. The Answers API processes questions asynchronously, so clients submit a question and poll for its result. See the API quickstart for authentication and request examples. The API tab contains the generated endpoint reference.

​
Authentication and limits

Interactive MCP and CLI sessions can use OAuth. Headless CLI jobs, token-based MCP connections, and REST requests use an API token. Personal and team tokens have different access scopes. Team token access can also be limited to selected data sources when the token is created. Store tokens in a secret manager and give each automation only the access it needs. Request and tool-call limits depend on the interface and token type. See rate limits for the current values.