Skip to main content

MCP Server

Normally, checking on an agent or fixing something in Flametree means opening the portal and clicking through screens yourself. MCP (Model Context Protocol) is an open standard that lets an AI assistant — the same kind of assistant developers use to write code, called a coding agent — connect to other services and act on them directly. The Flametree MCP server is our implementation of that standard: once it's connected, you can ask your coding agent, in plain English, to check a conversation, test an agent, or fix a configuration — and it does the work for you, in the chat window you're already using.

You don't need to know how to code to use it. If you can type a sentence describing what you want, you can use it.

Nothing changes without your say

Before your coding agent changes anything — creates an agent, edits a channel, moves something between environments — it shows you the plan first. It only goes ahead once you say yes.

Install it from the repository​

For developers: if you already work with a coding agent, you can skip the rest of this page. The Flametree MCP server lives at gitlab.enfint.ai/flametree/flametree-agent-mcp, and you can read its README without signing in. Paste the repository's own install request into your agent:

Install the latest stable Flametree MCP release for the client you are running in, following the installation instructions in this repository:
https://gitlab.enfint.ai/flametree/flametree-agent-mcp

Then ask it to sign you in to Flametree. For the full install, authentication, and troubleshooting steps, see the repository's installation guide.

New to this, or not sure what a coding agent is? Read What it's for, then follow Quick start — it covers everything from installing the app to a connected server.

Portal, MCP, or API — which should you use?​

Flametree doesn't make you choose one way to work — these are three doors into the same platform, and you can mix them.

OptionChoose it when...
The portalYou want to click through screens yourself: build an agent, read a session, check a dashboard. This is the default way to use Flametree — everything below is an optional shortcut on top of it, and nothing here replaces it.
MCP server + a coding agentYou already work through a coding agent and would rather describe what you want in plain English than switch tabs to the portal. Best for the kind of task you'd otherwise repeat by hand: checking a session, testing an agent, promoting a config between environments.
Public APIYou're building your own integration, script, or automation, with no chat assistant or portal screen in the loop. See the API Reference and the Chat API.

What it's for​

Point your coding agent at the MCP server and ask it, in plain language, to:

  • Diagnose a session — read the transcript, tool calls, and logs behind an answer, and point out the likely cause.

    Here's a link to a session. Work out why the agent answered incorrectly and tell me the most likely cause.

  • Test an agent — run through scripted scenarios (a successful path, missing or invalid answers, language switches) and report what broke, without changing anything.

    Test this agent: a successful scenario, then invalid answers and a language switch. Don't change anything — just report what you find.

  • Review recent activity — scan real sessions from a period, group recurring issues, and separate prompt problems from speech-recognition, platform, or channel problems.

    Check this agent's sessions from the last week and group the recurring problems by cause.

  • Create or change an agent — turn a description and source material into a working configuration, with a preview you approve before anything is applied.

    Create a support agent from this description and the material on our website. Show me the configuration before you create anything.

  • Manage channels and knowledge sources — connect, update, or troubleshoot integrations.

  • Handle operational tasks — promote an agent between environments, or investigate a voice/SIP incident.

Once MCP is connected

Ask directly: "What can you do with Flametree? Show me examples, without doing anything yet." An MCP server describes its own tools, so a connected agent can always list what it's capable of.

Is the MCP server ready for enterprise use?​

  • Nothing happens without your confirmation. Every action that changes data is shown to you as a plan first; the coding agent applies it only after you approve.
  • Access follows your existing role. The server signs you in with your own Flametree account and can only reach the tenants and environments that account already has access to in the portal — see Roles & permissions. It grants nothing beyond that.
  • Credentials stay out of view. Each environment keeps its own local sign-in token; error messages never include token values, and a failed sign-in only ever tells you the exact command to run again, never the credential itself.
  • Self-hosted deployments are supported. The server can point at your own on-premises Flametree installation and identity provider instead of the hosted environments.
  • The source is available, not a black box. The MCP server is released under the MIT license — your security team can read exactly what a tool does before you approve using it.

Before you start​

You need three things ready. Which coding agent app to use, and getting it installed and connected, is covered step by step in Quick start below — you don't need to arrange that in advance.

1. A coding-agent app. Use Claude Code Desktop or the Codex desktop app. The steps below stay inside the app you choose.

2. A paid plan or API billing for that coding agent. Claude Code needs an Anthropic account; we recommend Claude Pro. Codex needs an OpenAI account; we recommend ChatGPT Plus.

3. A Flametree account, and a browser on the same computer. The first time your coding agent uses a tool, it opens a sign-in page in your default browser — sign in there the same way you would to open the portal.

You don't need to install runtime helpers yourself. When the coding agent sets up the Flametree MCP plugin, it downloads the current plugin release and installs what the server needs.

Quick start​

Pick the coding agent app you want to use and follow its steps below, start to finish — from installing the app to a connected MCP server. Each path takes about 10 minutes. You only need to copy a few messages into the app and follow the prompts it shows you.

If you're not sure which agent to pick, ask a colleague which one your team already uses — both work the same way with Flametree.

Prefer to watch first? This short video walks through connecting a coding agent to the MCP server, start to finish.

If you don't want to pay for anything yet

Both agents need a paid plan or API billing to do real work — there's no free tier that's practical for this. If cost is a blocker, raise it with whoever manages tooling budget on your team before going further.

Claude Code Desktop — show the step-by-step instructions

  1. Get an Anthropic account and a plan. Go to claude.ai and sign up, then subscribe to a Claude plan (Pro or Max) — or, if your team prefers pay-as-you-go billing instead of a subscription, create API access at console.anthropic.com. Either one works with Claude Code.

  2. Download Claude Code Desktop. Open code.claude.com/docs/en/desktop, download the app for your computer, then open Claude and sign in with the Anthropic account from step 1.

  3. Open Claude Code, not regular Claude chat. In the Claude app, choose the Code tab. This is the coding-agent workspace that can set up the MCP server.

  4. Create a setup project. Start a new Code session and choose the folder where Claude should work. If the app asks for a project or session name, use something clear, such as Flametree MCP setup.

    Recommended setup settings

    Use Opus for the setup. Open the model dropdown next to the send button and choose Opus; you can change the model later from the same dropdown. To reduce setup prompts, open the permission-mode selector next to the send button and choose Auto accept edits or Auto, if your plan and organization allow it. Claude may still ask before sensitive actions; review those prompts before approving.

  5. Connect the Flametree MCP server. In the Claude Code prompt, paste this message and send it:

    Install the latest stable Flametree MCP release for the client you are running in, following the installation instructions in this repository:
    https://gitlab.enfint.ai/flametree/flametree-agent-mcp

    This can take a minute or two the first time. Claude Code shows what it is doing as it goes.

  6. Sign in to Flametree. In the same Claude Code chat, paste:

    Sign me in to Flametree, production environment.

    A browser tab opens with the Flametree sign-in page — sign in there, the same way you would to open the portal.

  7. Check that it worked. Return to Claude Code and ask:

    What Flametree MCP tools do you have available? List them.

    Claude Code should answer with a list of things it can now do with Flametree — diagnosing sessions, testing agents, and more. You can also open the app's MCP or Connectors view to see the connected flametree-agent-mcp server.

Codex desktop app — show the step-by-step instructions

  1. Get an OpenAI account and a plan. Go to chatgpt.com and sign up, then subscribe to a ChatGPT plan (Plus, Pro, or Team) — or, for pay-as-you-go billing instead of a subscription, create API access at platform.openai.com. Either one works with Codex.

  2. Download the Codex desktop app. Open chatgpt.com/download, install the app for your computer, then open it and sign in with the OpenAI account from step 1.

  3. Open Codex, not regular ChatGPT chat. In the app, choose Codex. This is the coding-agent workspace that can set up the MCP server.

  4. Create a setup project. Start a new Codex task and choose where it should work. If the app asks for a project or task name, use something clear, such as Flametree MCP setup.

    Recommended setup settings

    Use GPT-5.6 Sol for the setup. Open the model picker for the task and choose GPT-5.6 Sol. To reduce setup prompts, open the permissions control for the task and choose Approve for me, if your plan and organization allow it. Codex may still ask before sensitive actions; review those prompts before approving.

  5. Connect the Flametree MCP server. In the Codex prompt, paste this message and send it:

    Install the latest stable Flametree MCP release for the client you are running in, following the installation instructions in this repository:
    https://gitlab.enfint.ai/flametree/flametree-agent-mcp

    This can take a minute or two the first time. Codex shows the setup work as it goes.

  6. Sign in to Flametree. In the same Codex chat, paste:

    Sign me in to Flametree, production environment.

    A browser tab opens with the Flametree sign-in page — sign in there, the same way you would to open the portal.

  7. Check that it worked. Return to Codex and ask:

    What Flametree MCP tools do you have available? List them.

    Codex should answer with a list of things it can now do with Flametree — diagnosing sessions, testing agents, and more. You can also open Settings → MCP servers in the app to see the connected flametree_agent_mcp server.

You're connected — try the tip above to see what your agent can now do.

Tips​

Make it automatic

Most coding agents read a persistent instructions file (CLAUDE.md, AGENTS.md, or similar). Add a line like "Always use the Flametree MCP server when asked to inspect or operate on Flametree agents, sessions, or channels" so your agent reaches for it without being asked every time.

Approval mode

During initial setup, use Claude Code Desktop's permission-mode selector or Codex's permissions control to let the agent handle routine setup work. Keep reviewing any prompt that asks for sensitive access, login, or changes outside the setup project.

Ask when something is unclear

If the agent seems stuck, or you don't understand what it is doing, ask it to explain the issue and what is happening. Coding agents are usually good at turning setup errors into plain-language next steps.

Naming, if you connect several MCP servers

If another MCP server is already registered under the same name, give the Flametree one a distinct name when you set it up, or remove the conflicting entry from the app's MCP or Connectors settings before reinstalling.

Skills

The server ships with skills — ready-made playbooks for common workflows like testing an agent or reviewing recent sessions — that your coding agent picks up automatically once it's connected. Ask it "what Flametree skills do you have?" to see the current list.

What you can ask it to do​

These are real examples — adapt the wording to your situation, then paste the adapted version into your Claude Code Desktop or Codex desktop app chat (the same prompt from Quick start).

Diagnose a problem session

Here's a link to a <ProjectName /> session. Work out why the agent answered incorrectly and ended the conversation. Check the dialog, the tool calls, and the logs, then tell me the most likely cause.

Test an agent

Test this agent: run through a successful scenario, then incomplete and invalid user answers, a language switch, and an attempt to skip required questions. Don't change anything — prepare a report of what you find.

Review recent activity

Check this agent's sessions from the last week. Group the recurring problems and split them into prompt issues, speech-recognition issues, platform issues, and channel issues.

Create or change an agent

Create a support agent from this description and the material on our website. First prepare the requirements and show me the configuration. Apply the changes only after I confirm.

Two more advanced, operations-focused examples:

Move this agent from dev to prod along with its dependencies. Show me the plan, the differences, and what needs confirmation before you do anything.
Failed calls spiked in this voice campaign. Find the cause and prepare the data to hand to the SIP provider.

Common issues​

  • Your coding agent says it can't find the plugin or the MCP server. Start a new chat session — most coding agents only load newly installed plugins in a fresh session. Some also have a reload action in the app.
  • Nothing happens after you ask it to sign you in. Check that a browser window actually opened, and that you're signing in on the same computer where your coding agent runs — the sign-in callback needs both on one machine.
  • You're not sure which environment you're connected to. Ask your coding agent directly — "which Flametree environment am I connected to?" By default it's production; say the environment name explicitly if you need a different one.

Was this article helpful?