Teamo

com.teamo360Published by teamo360.comOfficial publisherv1.0.0Updated Oct 24, 2026

Search, edit, design, and undo: everything you can do in Teamo, now from your AI assistant

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Teamo connects an AI assistant to the Teamo workspace so it can search, edit and design content and undo changes from the assistant.

What you can do
Search content in Teamo from the assistant. Edit existing items in the workspace. Design new content or layouts. Undo changes made through the assistant. The registry description presents these as the same actions available in Teamo itself, but no individual tools are listed.
When to use it
Useful when you already work in Teamo and want an assistant to find, change or create content there without switching apps, or to roll back edits it made.
Requirements
OAuth authentication is required. It can be reached as a remote endpoint or run locally through the npm package @teamo360/mcp over stdio. No environment variables or headers are declared.
Before you install
The assistant can edit and design content in your Teamo workspace, so changes may affect shared or live material; undo is offered but review edits before relying on it. OAuth grants the server access to your Teamo account, and content is sent to Teamo's service.

Installation

In SourceWeft

  1. Open Teamo 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.teamo360%2Fteamo/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": {
    "teamo": {
      "type": "http",
      "url": "https://api.teamo360.com/api/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.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.