Hosted MCP server/Communication

Odichat MCP server

Provider setup path

Odichat manages a business inbox across WhatsApp, Instagram and Facebook from Claude. An agent can search conversations, update a sales pipeline and automate follow-ups. The MCP URL is per-account and embeds the personal token, so it must be copied from Odichat profile settings and treated as a secret. The public blog post does not document a fixed mcp.odichat.app endpoint.

Personal token embedded in the per-account MCP URL Server not checked yet Reviewed 2026-11-16
About

Where it fits

Sales and support teams that run their inbox in Odichat and want conversation and pipeline work in Claude.

  • Search conversations in a business inbox.
  • Update a sales pipeline from messages.
  • Automate follow-ups for inbox conversations.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Connect Odichat with your account URL

The MCP URL is per-account and embeds the personal token. Do not use the fixed mcp.odichat.app URL from older guides and do not share your URL.

  1. Copy your personal MCP URL

    Open Odichat profile settings and copy the MCP URL for your account. It contains a personal token.

  2. Add it as a remote server

    Paste that URL into the client's remote MCP field. Treat it as a secret.

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Odichat documentationhttps://odichat.app/blog/odichat-mcp-claude