Pally

com.pallyPublished by pally.comOfficial publisherv1.0.1Updated Oct 24, 2026

Chat with Pally, the AI assistant in your texts and on Telegram, from any MCP-compatible AI app.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Pally is a remote MCP server that lets an assistant connect to Pally, an AI assistant that works over text messages and Telegram.

What you can do
Connect an MCP-compatible AI app to Pally, an AI assistant reachable through texts and Telegram. The manifest lists no individual tools, so the exact actions available are not documented here. The connection is made to a hosted remote endpoint rather than a local package.
When to use it
Useful if you already use Pally for messaging-based assistance and want an MCP-compatible AI app to reach the same assistant. It is not a good fit if you need a documented set of specific tools before installing.
Requirements
A remote MCP connection to the hosted Pally endpoint. OAuth authentication is required, so a Pally account and a client that supports OAuth for remote MCP servers are needed. No environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, which grants an app access to your Pally account; review the permissions requested during authorization. No tools are listed, so what the assistant can read or change through Pally is unclear. Messages handled by Pally pass through a third-party service.

Installation

In SourceWeft

  1. Open Pally 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/com.pally%2Fpally/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": {
    "pally": {
      "type": "http",
      "url": "https://agent.pally.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

2
  1. v1.0.1LatestSep 22, 2026
  2. v1.0.0Sep 16, 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.