Data · Remote MCP server
Teamo
Search, edit, design, and undo: everything you can do in Teamo, now from your AI assistant.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.teamo360/teamo- Version
- 1.0.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-28
- Updated
- 2026-07-28
- Publisher
- com.teamo360
- Namespace
- Namespace verified by the MCP Registry via the domain teamo360.com · how
- Website
- teamo360.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.teamo360.com/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @teamo360/mcp | 1.0.0 | stdio |
How to connect Teamo
Teamo is a remote MCP server: there is nothing to install. Its endpoint is https://api.teamo360.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @teamo360/mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @teamo360/mcp@1.0.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"teamo": {
"command": "npx",
"args": [
"-y",
"@teamo360/mcp@1.0.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| Tclp MCPMCP server for The Chancery Lane Project's climate-aligned contract clause knowledge graph. | Remote · HTTPLive check: ✓ handshake |
| TCU Consolidada PJConsolidated lookup of a company at the Federal Audit Court (TCU) from the CNPJ, gathering sanctions. | Remote · HTTPLive check: ✓ handshake |
| TCU JurisprudênciaPublic search of the Brazilian Federal Court of Accounts (TCU) case law: keyword search across rulin. | Remote · HTTPLive check: ✓ handshake |
| Teamfight Tactics MCP ServerTeamfight Tactics data & AI coaching for Claude and ChatGPT - 19 tools, built-in Riot key. | Remote · HTTPLive check: sign-in required |
| TEAMWARS EsportsFPS esports data for AI: Valorant player stats, teams, tournaments, prizes from TEAMWARS. CS2 next. | Remote · HTTPLive check: sign-in required |
| TechEnthus Hardware Data APIAuthenticated GPU/CPU/PSU lookup; beta power-budget estimate. Coverage/freshness vary by source. | Remote · HTTPLive check: sign-in required |
| techmanual.aiSearch technical manuals for T&M, industrial automation, and power electronics equipment. | Remote & Local · HTTP, stdioLive check: sign-in required |
| TechnolifeUnofficial read-only Technolife: search electronics, compare sellers and installment prices, deals. | Local · stdio |