Confcall

app.confcallPublished by confcall.appOfficial publisherv0.1.1Updated Oct 24, 2026

Operate confcall.app video/phone rooms, notetaker, recordings, using your own confcall sk_ API key.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that lets an assistant operate confcall.app video and phone rooms, notetaker and recordings using your own confcall API key.

What you can do
  • Manage confcall.app video and phone rooms through the hosted MCP endpoint.
  • Work with the notetaker and with recordings of those rooms.
  • All actions are scoped to the account that owns the supplied API key.
When to use it
Useful when you want an assistant to help run confcall.app meeting rooms, notetaker sessions or recordings from a chat, without building your own integration.
Requirements
A remote streamable HTTP endpoint at mcp.confcall.app; no local package or runtime. A confcall API key (sk_live_ or sk_test_) sent in the X-API-Key header on every request. Network access to the hosted server.
Before you install
The server holds no key of its own, so your confcall API key is sent with every request; keep it out of shared logs and chats. Actions act on live rooms, notetaker and recordings in the key's account, so changes may affect real meetings and stored recordings. A live key can incur usage on your confcall account.

Installation

In SourceWeft

  1. Open Confcall in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.confcall%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "confcall": {
      "type": "http",
      "url": "https://mcp.confcall.app/",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.1LatestOct 14, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.