NEWPromptev MCP Server: one URL for every tool, every agent and your team’s knowledge. Connect Claude Code, Cursor, or any MCP client.→

Channels

Put it where people work.

Promptev lets one AI agent answer in the Promptev portal, Slack, WhatsApp, a chat widget on your website, the HTTP API and MCP clients, with the same knowledge, tools and approvals in every channel.

Start freeBook a demo

Support agent

“What is your refund window?”

Published once. Same knowledge, tools and approvals everywhere.

  • Promptev portalWeb chat

    What is your refund window?

    Orders can be returned within 30 days for a full refund.

    Returns policy

  • Slack#support

    Dana @Promptev What is your refund window?

    Promptev Orders can be returned within 30 days for a full refund.

  • WhatsAppBusiness number

    What is your refund window?

    Orders can be returned within 30 days for a full refund.

  • Website widgetYour site

    What is your refund window?

    Orders can be returned within 30 days for a full refund.

  • HTTP APIcurl

    POST /api/v1/agents/support/chat

    data: {"type":"token","content":"Orders can be returned within 30 days for a full refund."}

  • MCPAI client

    call_agent("support", "What is your refund window?")

    {"status":"ok","answer":"Orders can be returned within 30 days for a full refund."}

One published agent answers the same question in six places. Nothing is rebuilt per channel.

How it works

Build once, answer everywhere.

  1. Step 1

    Build and publish the agent once

    Give it instructions, knowledge and tools, and decide which actions need a person to approve them. Publishing makes that version live.

    One agent to maintain, not one per channel.

    Then choose where it answers.

  2. Step 2

    Switch on the channels you want

    Pick who may use it in the Promptev portal, a Slack channel, a WhatsApp number, the website domains allowed to embed it, and a project key for the API and MCP.

    Each channel is a switch on the same agent.

    People then ask wherever they already are.

  3. Step 3

    People ask where they already work

    Every channel runs the same published agent with the same knowledge, tools and approvals. Conversations in the portal, Slack, WhatsApp, the widget and the API are recorded with the channel they came from.

    Change the agent once and every channel has the change.

Who is asking

Each channel knows who it serves.

The agent is the same everywhere. What it may read depends on who is asking, so customers never see your internal files, even on the same agent.

ChannelWho uses itWhat it answers from
Promptev portalStaff and anyone you inviteSigned in. Answers from what each person may open.
SlackYour team, in a channel you pickMatched by Slack e-mail to a workspace member. Others get public knowledge.
WhatsAppCustomers and anyone with the numberPublic knowledge only.
Website widgetVisitors to the sites you allowPublic knowledge only.
HTTP APIYour own apps and scriptsA project key. Answers stream back.
MCPAI clients such as coding assistantsA project key. The agent is one tool call away.

Example

A support agent in six places.

A shop publishes one support agent that answers from its public returns and shipping pages. Customers reach it in the website widget and on WhatsApp. The support team asks it in Slack, where it can also read internal notes they may see. The order system calls it over the API. When the returns policy changes, the team updates one document and every channel answers with the new policy.

website widget: one tag
<script type="module"
  src="https://api.promptev.ai/embed/<token>/widget.js"
  data-position="right" async></script>
HTTP API: curl
curl -X POST https://api.promptev.ai/api/v1/agents/support/chat \
  -H "Authorization: Bearer <project key>" \
  -H "Content-Type: application/json" \
  -d '{"message": "What is your refund window?"}'
MCP: client config
{
  "mcpServers": {
    "promptev": {
      "url": "https://api.promptev.ai/api/v1/mcp/<workspace>/<project>/mcp",
      "headers": { "Authorization": "Bearer <project key>" }
    }
  }
}

Questions

Plain answers.

Where can a Promptev agent answer?

In the Promptev portal, in Slack, on WhatsApp, in a chat widget on your website, over the HTTP API, and in any AI client that speaks MCP (the Model Context Protocol). It is the same published agent in every one.

Does the agent know who is asking in each channel?

In the portal, people sign in, so each person gets answers from what they may open. In Slack, a sender whose Slack e-mail matches a workspace member gets their own access, and anyone else gets public knowledge only. On WhatsApp and the website widget, answers come from public knowledge only. The API and MCP use a key that belongs to one project.

How does the agent work in Slack?

Connect Slack to your project and choose a channel for the agent. People mention the app with their question, and it replies in a thread where they can keep asking without mentioning it again. People can also message the app directly.

Do approvals still apply outside the portal?

Yes. An action that needs approval waits in every channel, and an approver decides in the Promptev App or by e-mail. Nothing is sent, filed or changed until they do.

How do developers call the agent?

With a project API key, over a streaming HTTP endpoint or from an AI client connected to the project’s MCP address. Keys belong to one project and can expire or be revoked. Builders can also sign in to the workspace MCP from Claude, ChatGPT or any MCP client and build agents as themselves, no key needed.

Try it on your own documents.

2,500 free credits to start. No card, no seats.

Start freeBook a demo
2,500 free credits · No card required · No subscription
Start Free →Book a Demo