Context7

Fetch up-to-date code documentation and examples through remote MCP.

Family	Category	Sub-type	Auth type	Trending score
MCP Presets	mcp	dev-docs	custom	86

Overview

Product URL	API docs	Supported features
https://context7.com/	https://github.com/upstash/context7	tool_discovery, health_check, remote_mcp

Setup

1. Install the connector instance.
2. Store the custom remote endpoint or credentials.
3. Sync the remote MCP tool manifest after validation.
4. Review approval-gated write tools before running them.
5. No custom endpoint is required because the connector uses the fixed Context7 MCP server.

Auth & Configuration

• Chainabit uses the fixed Context7 MCP endpoint; no custom server URL is required.

Available Tools

This connector discovers tools dynamically from a remote MCP server. Run the sync step after storing credentials.

Examples

Install

CLI

chainabit connectors install context7 --name "Context7"

cURL

curl -X POST "$BASE_URL/connectors/instances" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "connectorKey": "context7",
  "displayName": "Context7"
}'

JavaScript

const response = await fetch(`${BASE_URL}/connectors/instances`, {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${TOKEN}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "connectorKey": "context7",
  "displayName": "Context7"
}),
});

Execute

CLI

chainabit connectors sync <instance-id>

cURL

curl -X POST "$BASE_URL/connectors/instances/<instance-id>/sync-tools" \
  -H "Authorization: Bearer $TOKEN"

JavaScript

await fetch(`${BASE_URL}/connectors/instances/<instance-id>/sync-tools`, {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${TOKEN}`,
  },
});

Security Notes

• Keep tokens, API keys, and connection strings in the encrypted credentials vault.
• Do not allow arbitrary server URLs for remote MCP connectors.
• Chainabit uses the fixed Context7 MCP endpoint; no custom server URL is required.

Troubleshooting

• If the health check fails, verify the token scope or credential payload and try again.
• Remote MCP connectors require trusted HTTPS endpoints only.

Back to the catalog