New

Your agent is now an MCP server

Connect Claude, Cursor, or any MCP client to your workspace agent — your product knowledge, answerable from wherever your team already works.

Your Asks agent knows your product better than any document does — so we made it callable from outside Asks. Every workspace can now expose its agent as a remote MCP server: connect it to Claude, Cursor, or any MCP-compatible client with an API key, and ask it questions from wherever you already work.

Your engineer can ask the agent about refund policy edge cases from inside their editor. Your ops team can query it from Claude while writing macros. Same knowledge, same guardrails — new front doors. And it works the other direction too: your agent can call your MCP servers as tools, configured under AI Agent → MCP Servers.

{ "mcpServers": {
    "acme-support": {
      "url": "https://api.asks.app/v1/mcp",
      "headers": { "Authorization": "Bearer ask_..." }
    }
} }

Connect a client in two steps

1
Turn on the MCP server
At Integrations → MCP, enable the server. You name the tool clients see, write the description that tells their LLMs when to call it, and can optionally expose a read-only search_knowledge tool over your published knowledge base.
2
Mint a key and connect
The page generates an API key with the right scopes and fills it into ready-to-copy snippets for Claude Code and Cursor. Any generic MCP client works the same way: HTTP transport, the endpoint URL, and a Bearer header — plain JSON-RPC over POST, no SSE stream or session to manage.

Configure and connect dialog on the Agent API page with the tool name and description fields and the expose knowledge-base search toggle — Name the tool, write its description, copy a connect snippet.

Availability

The MCP server is a Premium feature. Every question a client asks is a normal agent turn — it consumes AI credits by model tier and creates a real conversation, so MCP exchanges show up in your inbox like any other channel.

The other direction: tools for your agent

Under AI Agent → MCP Servers, your agent can consume external MCP servers as tools. Add a server by URL, pick the authentication — none, bearer token, or an API-key header, with secrets encrypted at rest — and Asks discovers its tools (up to 40 per server). Each tool gets its own switch, so you control exactly what the agent may call; an enable switch pauses a whole server without deleting it, and if a tool call fails mid-conversation, the agent answers without it rather than exposing the error to the customer.

MCP Servers page with the Add server button, the how-it-works explainer, and the servers usage meter

Connected MCP server card showing the connected status badge, the Enable server switch, and the tools list with per-tool switches

Plans allow 1 connected server on Starter, 3 on Business, and 10 on Premium. Prefer custom actions when the capability is a plain HTTP call against your own API; reach for MCP when a system already speaks the protocol or ships many tools at once.

Go deeper

DocsMCP server→DocsMCP servers for your agent→DocsAuthentication→

← Newer · Jun 24, 2026Three new channels: Telegram, Slack, and Discord Older · Jun 20, 2026 →The Asks public API, plus outbound webhooks

Try it yourself

See what's new in your workspace

Everything on this page is live today. Asks trains on your website and resolves customer conversations on every channel — free to try, live in minutes.

Start free All updates