Talk to OneHub360 from Claude or ChatGPT
OneHub360 ships a hosted MCP (Model Context Protocol) server so AI agents can read and write your CRM, pipeline, inbox, and proposals in plain language. Endpoint: https://onehub360.com/api/mcp. Mint a key in Settings → API Keys, paste the config below into Claude Desktop / Claude Code / ChatGPT.
Questions, integration help, or feedback? Email dev@onehub360.com - it routes to a human.
Connect in 30 seconds
Mint a key in Settings → API Keys, paste the snippet, restart your agent. The hosted endpoint is live; a local stdio server is also available for self-host scenarios.
{
"mcpServers": {
"onehub360": {
"url": "https://onehub360.com/api/mcp",
"headers": {
"Authorization": "Bearer nhk_<your_key>"
}
}
}
}{
"mcpServers": {
"onehub360": {
"command": "node",
"args": ["/path/to/oh360-mcp/dist/index.js"],
"env": {
"OH360_API_KEY": "nhk_<your_key>",
"OH360_DEFAULT_BUSINESS_ID": "<your_business_id>"
}
}
}
}| Tool | What it does |
|---|---|
| oh360_whoami | Diagnostic: confirm the MCP is wired up and which business it points at. |
| oh360_search_contacts | Search by name, email, phone, or company. Paginated. |
| oh360_get_contact | Fetch a single contact by id. |
| oh360_list_deals | List pipeline deals, optionally filtered by stage. |
| oh360_get_deal | Fetch a single deal with linked contact and history. |
| oh360_list_tasks | List tasks and reminders, filterable by status or assignee. |
| oh360_get_task | Fetch a single task with assignee and business. |
| oh360_list_proposals | List proposals (lite) with status, sent/viewed timestamps, version. |
| oh360_get_proposal | Fetch a proposal with full sections, HTML, cover email, and linked contact/deal. |
| oh360_list_invoices | List invoices, filterable by status or contact. |
| oh360_get_invoice | Fetch an invoice with line items, payments, and linked contact/deal. |
| oh360_list_email_threads | List inbox conversations (email/SMS/call) with last-message preview. |
| oh360_get_email_thread | Fetch all messages in an inbox conversation thread. |
| oh360_list_chats | List live-chat conversations (visitor sessions). |
| oh360_get_chat_messages | Fetch messages in a chat conversation. Read-only - does not mark as read. |
| oh360_list_businesses | List businesses the API key / user can access. |
| oh360_get_tenant | Fetch tenant: plan, subscription, branding, custom domain. |
| oh360_dashboard_stats | Aggregate metrics: pipeline value, revenue this/last month, pending tasks, today’s appointments. |
| oh360_global_search | Cross-object search across contacts, businesses, deals, tasks, conversations. |
https://onehub360.com/api/mcp are all live today. Still in the works: replying to an email thread from your agent. Signing in with your OneHub360 account instead of an API key is planned.- oh360_reply_to_email
Run your CRM from Claude
Search contacts, move deals, send proposals - all in plain language.
Send invoices from ChatGPT
Generate, preview, send - with explicit confirm:true.
AI agent for small business
Connect any AI agent to your CRM, pipeline, inbox.
Send proposals from Claude
Pull deal context, draft, preview, send.
API key auth, scoped per business.
Every MCP key is bound to a single business in your tenant. An agent connected with that key cannot read or write to any other business, even if you have multiple. Keys are SHA-256 hashed on our side - we never store the raw value.
Plan tier gating.
Read tools are available on Starter and above. Write tools need Growth or higher, and delete tools need Pro or higher. The Free plan has no API access. The MCP's tools/list response is filtered by your plan, so agents only ever see what they're allowed to call.
Mutation safety.
Send and delete actions require an explicit confirm: true. Without it, the call is refused and nothing is sent or removed. Combined with idempotency keys, agents can't accidentally fire the same proposal twice or hit the wrong contact in a retry loop.
Idempotency.
If you set an Idempotency-Key header on the outer MCP request, OneHub360 derives per-tool-call keys from it (${outerKey}:${toolName}:${callIndex}). A retry with the same outer key produces the same response per tool call - agents get safe retries on flaky networks without double-creating contacts, deals, or invoices. Different bodies under the same outer key + tool combo return 409 IDEMPOTENCY_CONFLICT; generate a fresh key rather than reusing one for a different operation. Read tools never forward the key.
Audit log.
Write and delete calls are recorded in your audit log with the API key, tool name, arguments (secrets redacted) and response status. The API key cache lasts 60 seconds, so revoking a key from Settings → API Keys kills it within a minute.
Ready to talk to your CRM?