Agent setup.

MCP

• Server: https://ctx4.me/mcp.
• Transport: Streamable HTTP.
• Human sign-in: browser OAuth, without issuing a Context4 API key.
• Resource discovery, OAuth discovery.
• Console and accounts.

Start with this page. Open other material for the step you are working on. Documentation and an MCP configuration entry do not prove access to data.

1. Identify the client

Identify the application from reliable environment context, not the model. If unknown, ask once: ChatGPT, Claude, Codex, Claude Code, Hermes, OpenClaw, or another MCP client?

Cloud clients cannot reach localhost documentation or a local MCP server. Stop and explain the need for a reachable HTTPS deployment. Do not invent a domain or silently substitute the production server.

2. Skills and client configuration

Check existing Context4 skills and tools. Reuse a suitable MCP connection. Do not overwrite another configuration or edited files without consent.

For normal operation, install context4 and context4-setup; add context4-workflows for tasks across systems. File manifest and SHA-256, package descriptions. Read the whole package before saving it, including references. If the client cannot persist skills, use this guidance in the current chat and state that there is no persistent installation.

Open only the pair of links for your client:

If the chat cannot change client settings, show exact manual steps. The user confirms sign-in, workspace, and consent. Wait for MCP tools to appear; explain a restart or new chat if needed. Installing a skill does not create an OAuth grant.

Other MCP clients

For an unlisted client, use its native remote Streamable HTTP MCP configuration with the address above and OAuth discovery. Check skill storage against the actual client's documentation; a standard package contains SKILL.md and references. Do not guess configuration paths or CLI flags. If persistent skills are unsupported, use the guidance for this conversation and state the limitation explicitly.

3. Core tools

The global /mcp endpoint provides five meta-tools. Use the actual client's schemas; see the full reference.

Do not guess tool slugs or use another product's tools. COMPOSIO aliases are permitted only in a session that actually lists them.

4. Connect a business account

If the task or service is unknown, ask. Discover a suitable read, fetch its schema, and inspect connections. Ask the user to choose when multiple accounts are available. If authorization is needed, obtain a link through CONTEXT4_MANAGE_CONNECTIONS, show it to the user, and wait for actual readiness through CONTEXT4_WAIT_FOR_CONNECTIONS, respecting retry hints. Do not construct an authorization URL manually or request secrets in chat.

5. Confirm readiness with a read

Perform one permitted read through CONTEXT4_MULTI_EXECUTE_TOOL. Inspect every result. A successful empty response means the query works but has no matching data. Pending status, an error, a discovered schema, or a displayed link does not yet prove readiness. If no read is available, explain the limitation; do not create a record as a test.

Briefly report the connected service/account, what was checked, and a useful next task. Writes, deletions, and messages must stay within the user's instruction.

As needed

Providers, errors and MCP, connections, revoking access, all chapters. For server integrations: API, SDK/proxy. Do not load the full API reference for ordinary MCP setup.

For a person: open the HTML instructions.

Data and terms

Context4 is free. Operation content is proxied without persistent storage. Account and authorization data is processed separately. Data handling · Privacy · Terms · Support and deletion.