Atmita

com.atmitaPublished by atmita.comOfficial publisherv1.0.1Updated Oct 24, 2026

Message your Atmita agent - one connection reaches all its accounts and tools, WhatsApp included.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant message your Atmita agent, reaching all of its connected accounts and tools, WhatsApp included.

What you can do
  • Send messages to your Atmita agent through a single connection.
  • Reach every account and tool that agent has connected, including WhatsApp.
  • No tool list is published, so the exact actions available depend on what your Atmita agent is configured with.
When to use it
Use it when you already run an Atmita agent and want an AI assistant to hand it messages or tasks that span its connected accounts and tools, rather than wiring each service separately.
Requirements
A remote MCP endpoint at mcp.atmita.com over streamable HTTP, with OAuth sign-in required. An Atmita account and an agent with connected accounts and tools are implied by the description.
Before you install
The connection can reach every account and tool your Atmita agent is linked to, WhatsApp included, so messages may trigger actions or send data through those services. Access is granted via OAuth; review the scopes you approve. No tool list is published, so verify what the agent can do before connecting.

Installation

In SourceWeft

  1. Open Atmita 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.atmita%2Fatmita/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": {
    "atmita": {
      "type": "http",
      "url": "https://mcp.atmita.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.1LatestSep 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.