MCP

The Bulkgrid MCP server gives AI clients tools to inspect accessible collections and search indexed content.

https://bulkgrid.com/api/v1/mcp

Connect with OAuth

Client setup

Choose your client, add Bulkgrid, and sign in through your browser. Review the workspace and collections the agent can access.

Codex
Claude Code
Cursor
OpenCode

Run in your terminal with the Codex CLI installed:

codex mcp add bulkgrid --url https://bulkgrid.com/api/v1/mcp

Complete the browser sign-in if prompted. To start sign-in separately, run codex mcp login bulkgrid. Open a new Codex session after connecting.Codex MCP setup

Run in your project’s terminal with Claude Code installed:

claude mcp add --transport http bulkgrid https://bulkgrid.com/api/v1/mcp

Open Claude Code, run /mcp, and select bulkgrid to authenticate in your browser.Claude Code MCP setup

Add this server to .cursor/mcp.json in your project. If the file already contains servers, add bulkgrid inside its existing mcpServers object.

.cursor/mcp.json

{
  "mcpServers": {
    "bulkgrid": {
      "url": "https://bulkgrid.com/api/v1/mcp"
    }
  }
}

Open Cursor’s MCP settings, enable bulkgrid, and complete the browser authentication when prompted.Cursor MCP setup

Run OpenCode’s interactive setup:

opencode mcp add

Choose a remote server, name it bulkgrid, and enter https://bulkgrid.com/api/v1/mcp. Then sign in:

opencode mcp auth bulkgrid

OpenCode MCP setup

Open Settings → Connected Apps in Bulkgrid and copy the MCP URL.
Add a remote MCP server in your AI app. Use OAuth with automatic client registration.
Sign in to Bulkgrid in the browser, review the preselected workspace, choose collection access, and approve.
Return to your AI app and enable the Bulkgrid tools.

Use this flow in ChatGPT, Claude, Cursor, or another client that supports remote MCP with OAuth and automatic registration. Client setup screens vary; use the app’s remote server or custom connector settings. You do not need to create an OAuth application, supply a callback URL, or copy a client secret.

Permissions

OAuth grants mcp:use and search:query for the approved workspace and collections. A tool’s collection filter can narrow these permissions but cannot expand them. Your user must remain a member of the workspace. Each user/client grant stays bound to one workspace, including after reauthorization. Use a separate client connection for another workspace. Manage and revoke access under Settings → Connected Apps. Search returns passages from indexed content; connecting an app does not automatically ingest new sources. Add sources and check indexing before testing search.

Connect with an API key

For clients configured through bearer headers, create a key with mcp:use and search:query:

Authorization: Bearer bg_live_your_api_key

The server also accepts x-api-key. Use one authentication method per connection. The CLI can configure supported clients:

export BULKGRID_MCP_URL='https://bulkgrid.com/api/v1/mcp'
export BULKGRID_API_KEY='bg_live_your_api_key'
npx -y @bulkgrid/cli init --all

Use --cursor, --vscode, --claude, or --codex for one client. Each AI app owns its connection; a separate bulkgrid login session does not authenticate the AI app.

Existing installation URLs

Installation-specific URLs have been retired. Replace them with the shared /api/v1/mcp URL and approve access again.

Troubleshooting

Symptom	Check
OAuth setup cannot start	The client supports automatic OAuth registration and the URL is the shared MCP endpoint
`401`	The token is invalid or expired, or the authentication header is missing
`403`	Connection revocation, membership, collection restrictions, or missing scopes
No results	Sources are indexed and included in the approved collections
GET returns `405`	MCP requests use POST; opening the endpoint in a browser is not a connection test

Suggested agent instruction

Use Bulkgrid to search indexed source content and ground answers in the collections available to this connection. Include source URLs when citing retrieved content.

Source management through scoped API keys

The source-management tools in the repository build are available only to API-key connections, with mcp:use plus the operation scopes below. OAuth remains search-only. Tool availability depends on the deployed server version and the key’s scopes; an agent should inspect its connected tools.

Tools	Required operation scopes
`find_sources`, `get_source_status`	`sources:read`
`get_source_analysis`	`sources:discover`
`analyze_source`	`sources:discover`, `runs:write`
`add_source`	`sources:write`
`recrawl_source`	`sources:write`, `runs:write`
`list_source_collections`, `get_collection_rules`	`collections:read`
`add_source_to_collection`	`collections:write`

Use analyze_source to start asynchronous analysis, then get_source_analysis to read candidate paths, URL counts and warnings. Analysis can create a crawl run and consume resources. Adding a source can establish ongoing refresh; including it in a collection grants retrieval over its eligible documents. The API enforces workspace, collection and plan restrictions. A key’s technical permissions do not replace the user’s instructions about permitted sources, visibility, scope and budgets. Success payloads are exposed as structuredContent.result; API failures are tool errors with status and error details. Check source status before describing content as searchable. The bulkgrid-sources skill in the developer repository guides this workflow; bulkgrid-search handles answering from indexed content.

Get started

Index

More

Access and operations

Connect with OAuth

Client setup

Permissions

Connect with an API key

Existing installation URLs

Troubleshooting

Suggested agent instruction

Source management through scoped API keys

​Connect with OAuth

​Client setup

​Permissions

​Connect with an API key

​Existing installation URLs

​Troubleshooting

​Suggested agent instruction

​Source management through scoped API keys

Connect with OAuth

Client setup

Permissions

Connect with an API key

Existing installation URLs

Troubleshooting

Suggested agent instruction

Source management through scoped API keys