Productivity · Remote MCP server
Onboard
Your AI copilot for customer onboarding - projects, KPIs, tasks, and safe writes.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.viaonboard/onboard- Version
- 0.1.1
- Status
- Active
- Category
- productivity
- Transport
- SSE (HTTP + Server-Sent Events), Streamable HTTP
- Published
- 2026-06-18
- Updated
- 2026-06-18
- Publisher
- viaonboard (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/viaonboard) · how
- Website
- docs.onboard.io/docs/mcp
- Repository
- github.com/viaonboard/onboard-platform
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| SSE (HTTP + Server-Sent Events) | https://rest.onboard.io/mcp/sse | None |
| Streamable HTTP | https://rest.onboard.io/mcp/rpc | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://rest.onboard.io/mcp/sse(SSE)- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://rest.onboard.io/mcp/rpc(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Onboard
Onboard is a remote MCP server: there is nothing to install. Its endpoint is https://rest.onboard.io/mcp/rpc, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
It also lists an endpoint on the older SSE transport https://rest.onboard.io/mcp/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| OmnierTurn signals from email, CRM, and meetings into a prioritized daily sales to-do list. | Remote · HTTPLive check: sign-in required |
| OmniFocusFull CRUD MCP server for OmniFocus via Omni Automation - tasks, projects, folders, tags, recurrence. | Local · stdio |
| OmniSignalLive market intelligence & AI content strategy: trends, competitor moves, content calendar. | Remote · HTTPLive check: sign-in required |
| On BoardCross-platform shared memory and ticket coordination for AI agents across MCP clients. | Local · stdio |
| OnboardingNew-hire onboarding: role-based task templates, day-one to day-ninety checklists, completion. | Remote · HTTPLive check: ✓ handshake |
| OneFind, document and execute authenticated API calls across 700+ apps via one MCP server. | Remote & Local · HTTP, stdioLive check: sign-in required |
| OneLoreShared project context for AI agents and teams: docs, tasks, and messages that stay current. | Remote · HTTPLive check: sign-in required |
| OnfidoCreate and read Onfido applicants, documents, checks and reports. | Remote · HTTPLive check: ✓ handshake |