MCP connectors

این محتوا هنوز به زبان شما در دسترس نیست.

Entergram ships a hosted MCP server. Point an AI client at it and the agent can read chats, send messages, manage tickets and update custom fields in plain language.

Settings → Developers → MCP

Connecting a client

Go to Settings → Developers → Connectors (API & MCP) and pick your platform — Claude, ChatGPT, Perplexity, Make, n8n or Custom.
Copy the MCP server URL.
Paste it into your AI app as a connector.

“To connect, just paste this URL into {platform} — no other setup needed.”
Authorize the scopes you want to grant.

That’s it for most clients. Everything else is under Advanced settings.

Client authentication

Method	Use it for
Browser sign-in, no secret (public + PKCE)	Claude Web, Claude Desktop, local apps
Client secret in request body (`client_secret_post`)	Server-side automation
Client secret in Authorization header (`client_secret_basic`)	Server-side automation

Claude Web and local apps should usually use browser sign-in with PKCE. Server-side automation can use a client secret.

For a public client: “This client uses browser sign-in with PKCE. Leave the client secret blank in Claude.”

Scopes

Grant the minimum the agent actually needs.

Scope	Grants
`workspace.read`	Workspace details
`members.read`	Team members
`accounts.read`	Connected accounts
`contacts.read`	Contacts
`chats.read` / `chats.write`	Chats / edit chats
`chat_custom_fields.read` / `.write`	Chat custom fields / edit them
`messages.read` / `messages.write`	Messages / send messages
`custom_fields.read` / `.write`	Custom fields / edit them
`tickets.read` / `tickets.write`	Tickets / edit tickets
`offline_access`	Stay connected (refresh tokens)

messages.write lets an agent send Telegram messages as you. Grant it deliberately.

Two kinds of client

	Personal agents	Workspace clients
Scope	Your seat only	The whole workspace
Who manages	You	Owners and admins
Typical use	Claude Desktop, Codex, your own n8n	Shared team integrations
Available scopes	Seat-safe read scopes, actor-scoped chat custom fields, offline access	Full scope set

Members can create personal clients. Only owners and admins can create workspace clients.

What an agent can actually do

Practically everything in the product, driven by a sentence:

“Send our promo to every chat whose Customer tier field is VIP.”
“Mark every unread group as read and set its Campaign field to Q3.”
“Open a high-priority ticket for every chat that hasn’t had a reply in 5 days, and assign them to me.”
“Which chats have no Stage set? Set them all to New.”

Broadcasts, bulk edits, custom columns and tickets are all reachable.

Requirements

API & MCP is a Pro feature.
Personal clients are private to your seat; workspace clients need owner/admin rights.

Security notes

Client secrets are shown once. Entergram stores only a hash — after the dialog closes you can rotate the secret, never reveal it.
Redirect URIs: one per line, HTTPS required outside localhost.
PKCE is mandatory for public clients and recommended even for confidential ones.
Revoking a grant immediately removes stored refresh tokens; the client must complete OAuth again to reconnect.
Archiving a client disables it and revokes its active grants and refresh tokens.

Personal agents
Workspace OAuth clients
Public API keys — for integrations that aren’t MCP clients