MCP Registry
Find Onboard on the official Model Context Protocol Registry — listing ID, hosted endpoints, and how to connect.
Onboard is published on the Model Context Protocol Registry,
the official catalog of MCP servers. The registry stores metadata only (name,
endpoints, auth hints, capabilities)—not your data. Onboard MCP itself remains a
hosted remote server on rest.onboard.io; you connect with the same URLs and
credentials described in MCP setup and
Connecting to Onboard MCP.
Find Onboard in the registry
| Field | Value |
|---|---|
| Registry name | io.github.viaonboard/onboard |
| Display title | Onboard |
| Listing version | 0.1.0 |
| Status | Active |
| Documentation | MCP overview |
Search or open the listing directly:
registry.modelcontextprotocol.io — Onboard
Registry vs. your tenant
The registry tells clients where Onboard MCP lives and how to authenticate. You still need an Onboard subscription with MCP, an API key (or OAuth sign-in where supported), and the same permissions as any REST integration. The registry does not provision accounts or bypass your org’s access controls.
What the listing includes
The published manifest describes a remote MCP server with two transport options:
| Transport | Production URL |
|---|---|
| SSE (session stream; default “MCP URL” in most clients) | https://rest.onboard.io/mcp/sse |
| Streamable HTTP (JSON-RPC) | https://rest.onboard.io/mcp/rpc |
Capabilities advertised in the registry:
- Tools — workflow tools (search customers, KPIs, tasks, previews) plus curated
[API]browse/explain/read/write helpers - Prompts — reusable onboarding playbooks (weekly summary, kickoff builder, risk review, and more)
- Resources — stable context schemas (customer/project model, status vocabulary, API constraints)
Auth hints in the listing point clients to:
- OAuth discovery —
https://rest.onboard.io/mcp/.well-known/oauth-protected-resource(RFC 9728; used by OAuth-only connectors such as Claude custom connectors) - Connection docs — Connecting to Onboard MCP
Tags: onboarding, customer-success, project-management, CRM, tasks
Source repository: github.com/viaonboard/onboard-rest-api (onboard_mcp subfolder)
Connect after discovering the listing
Registry-aware MCP clients may pre-fill URLs from the listing. You still complete setup in your org:
- Confirm MCP is on your plan and you have an Admin who can manage API keys.
- Copy your API key from Settings → Integrations → API (or use OAuth per user where the client requires it).
- Enter the SSE URL
https://rest.onboard.io/mcp/sseunless the client documentation specifies Streamable HTTP or RPC instead. - Follow the client-specific guide under MCP desktop clients.
For OAuth Client ID fields, Inspector testing, and auth comparison tables, see Connecting to Onboard MCP.
Why the registry matters
- Discovery — Teams and tool vendors can find a canonical Onboard MCP entry instead of copying ad hoc URLs.
- Client integration — MCP hosts that support registry lookup can wire endpoints and auth metadata automatically.
- Transparency — Version, capabilities, and documentation links are visible before you connect.
If a client does not yet support registry import, use the same production URLs and auth steps above—the server behavior is identical.
Related
- MCP setup — base URL, endpoints, API key requirements
- Connecting to Onboard MCP — OAuth vs API key, Inspector, Client ID
- Security & permissions (MCP) — keys, tenancy, reviews
- MCP desktop clients — Claude, Cursor, Amazon Quick, and others
How is this guide?