> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getunblocked.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Programmatic access to Unblocked

> Choose MCP, the Unblocked CLI, or the REST API for agents, scripts, CI jobs, and custom integrations

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

| What you need                                                                | Use                                                |
| ---------------------------------------------------------------------------- | -------------------------------------------------- |
| Give an AI coding agent access to Unblocked context                          | [MCP](#mcp-for-coding-agents)                      |
| Connect an MCP client without installing a local binary                      | [Remote MCP](#choose-a-remote-or-local-connection) |
| Configure supported coding agents on macOS or Linux with one install command | [Local MCP](#choose-a-remote-or-local-connection)  |
| Query Unblocked from a shell script or CI job                                | [Unblocked CLI](#cli-for-scripts-and-ci)           |
| Search one source type or retrieve filtered issues and pull requests         | [Unblocked CLI](#cli-for-scripts-and-ci)           |
| Add documents from a custom data source                                      | [REST API](#rest-api-for-custom-integrations)      |
| Ask questions from a backend service                                         | [REST API](#rest-api-for-custom-integrations)      |

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](/unblocked-mcp/mcp-overview) 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.

<Tabs>
  <Tab title="Remote MCP">
    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.

    <Warning>
      Select HTTP when your MCP client asks for a transport. Unblocked does not support the deprecated HTTP+SSE transport.
    </Warning>

    See [Remote MCP setup](/unblocked-mcp/install-other#remote-mcp).
  </Tab>

  <Tab title="Local MCP">
    On macOS and glibc-based Linux, the Unblocked CLI runs the MCP server on your computer. The installer can configure supported coding agents and install the Unblocked skills in one step.

    Choose Local MCP when you also want the CLI, when your client requires stdio, or when you want one installer to configure the supported tools on your computer.

    See [MCP installation](/unblocked-mcp/mcp-overview#install-macos-and-linux) or [manual local setup](/unblocked-mcp/install-other#local-mcp-macos-and-linux).
  </Tab>
</Tabs>

## CLI for scripts and CI

The [Unblocked CLI](/unblocked-cli/cli-overview) 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:

<CardGroup cols={3}>
  <Card title="Install the CLI" icon="download" href="/unblocked-cli/cli-install" />

  <Card title="Authenticate" icon="key" href="/unblocked-cli/cli-auth" />

  <Card title="Query your workspace" icon="terminal" href="/unblocked-cli/cli-query" />
</CardGroup>

## REST API for custom integrations

The [Unblocked REST API](/api-reference/quickstart) 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](/api-reference/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](/api-reference/rate-limits) for the current values.