Connect your assistant to NoInfra

1. Add the HTTP endpoint

Use Streamable HTTP at https://mcp.noinfra.ai/mcp. The server currently negotiates MCP protocol 2025-03-26. The host root is not the protocol endpoint.

# Claude Code
claude mcp add --transport http noinfra https://mcp.noinfra.ai/mcp

# Other compatible clients
# Add a remote Streamable HTTP MCP server with this URL:
https://mcp.noinfra.ai/mcp

2. Run a public read

Initialize the connection and list tools. Public discovery needs no bearer token. These calls do not provision an agent, spend funds or send messages.

• noinfra.services.list — inspect the services available to this caller.
• noinfra.catalog.get — read current product information and next steps.
• noinfra.recommend_agent — describe a workflow and receive a suggested starting point. This is guidance, not deployment or an eligibility check.

{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"your-client","version":"1.0"}}}

3. Request private access

External-agent Email is a limited verified-account pilot. Confirm eligibility with the founding team before attempting setup. An eligible account owner authorizes a connection in NoInfra. Compatible clients can discover the OAuth authorization server through the MCP protected-resource metadata. Do not paste account passwords or private bearer tokens into prompts.

Understand the permission boundary

The public catalog does not grant access to Brain, Wallet, Phone or other hosted-agent capabilities. Availability depends on the credential type, account, agent and current grants. External Email access advertises email:provision, email:read and email:draft scopes; sending follows owner review.

Handle failures and retries

• 401: obtain or renew owner authorization through the advertised authorization flow. Do not bypass account eligibility.
• 403 or an unavailable capability: check current account and agent permissions; request access from the owner.
• Timeout or uncertain write: keep the same idempotency key and inspect the existing operation before retrying. A timeout does not prove failure.
• Approval required: show the owner the exact proposed action and wait for the supported approval flow.
• After revocation: discard old access and refresh discovery. Never reuse a saved token to evade the owner's decision.

Choose a business workflow

Start with one bounded job, a named reviewer and clear acceptance criteria. The guides use synthetic examples and do not represent customer results or ready-to-purchase templates.