Protocol

Remote MCP agents.

Remote MCP is the fastest path when your app already exposes a Model Context Protocol server. Orchet reviews and snapshots tools/list during approval, and reviewers will flag any auth or transport combination that needs platform support before publishing.

Submission payload.

Submit server metadata, OAuth endpoints, scopes, transport, and contact email. Do not include OAuth client credentials in the payload.

SHELL

ORCHET_DEVELOPER_TOKEN=... orchet-agent submit-mcp \
  --server-id honeybook \
  --display-name "HoneyBook" \
  --mcp-url https://mcp.honeybook.com \
  --authorize-url https://app.honeybook.com/oauth/authorize \
  --token-url https://api.honeybook.com/oauth/token \
  --transport streamable_http \
  --scopes projects:read,clients:read \
  --contact-email developer@example.com

Review.

Trust checks probe initialize, fetch tools/list, snapshot names/descriptions/input schemas, and classify scopes. Runtime calls use tools/call after the agent is approved and the user is connected. If your MCP server requires a transport or auth pattern Orchet cannot support yet, reviewers will mark the submission as pending changes instead of publishing an unusable agent.

OAuth client setup.

During approval, Orchet admins configure ORCHET_MCP_<SERVER_ID>_CLIENT_ID and optional _CLIENT_SECRET in the platform environment. The submission references endpoints and scopes; credentials stay out of developer-submitted JSON.