Telvana

io.github.telvana-aiPublished by GitHub account telvana-aiv1.0.0Updated Oct 24, 2026

Manage your Telvana AI voice, SMS and chat agents, conversations, campaigns and outbound calls.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant manage Telvana AI voice, SMS and chat agents, conversations, campaigns and outbound calls through a remote endpoint.

What you can do
Telvana exposes a remote MCP endpoint for managing AI voice, SMS and chat agents. According to the registry description, it covers agents, conversations, campaigns and outbound calls, so an assistant can work with these resources on the Telvana platform. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Use it when you already run Telvana AI voice, SMS or chat agents and want an assistant to help manage them, their conversations, campaigns or outbound calling from within a chat session.
Requirements
A remote MCP connection to the Telvana endpoint over streamable HTTP, plus OAuth sign-in with a Telvana account. No local runtime, packages, environment variables or headers are declared.
Before you install
The server requires OAuth authorization to your Telvana account, which likely grants access to agents, conversations and campaigns. Campaign and outbound-call management may send messages or place calls and could incur costs; confirm before letting an assistant make changes.

Installation

In SourceWeft

  1. Open Telvana in the dashboard and add it to a workspace.
  2. Connect the required 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/io.github.telvana-ai%2Ftelvana-mcp/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "telvana": {
      "type": "http",
      "url": "https://mcp.telvana.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 15, 2026

Score

67% 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
  • 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.