Developer · Remote MCP server
Ateam MCP
Build, validate, and deploy multi-agent AI solutions from any AI environment.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ariekogan/ateam-mcp- Version
- 0.1.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-02-17
- Updated
- 2026-02-17
- Publisher
- ariekogan (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ariekogan) · how
- Repository
- github.com/ariekogan/ateam-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.ateam-ai.com/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 | @ateam-ai/mcp | 0.1.2 | stdio |
How to connect Ateam MCP
Ateam MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.ateam-ai.com/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: @ateam-ai/mcp version 0.1.2. 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 @ateam-ai/mcp@0.1.2.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"ateam-mcp": {
"command": "npx",
"args": [
"-y",
"@ateam-ai/mcp@0.1.2"
]
}
}
}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 developer servers
| Server | Runs |
|---|---|
| Asuswrt MCPSecure AsusWRT router administration via SSH - 42+ tools, guarded mutations. | Local · stdio |
| Async Parallel Antigravity for Codex & Claude CodeRun parallel, resumable, human-operable Antigravity CLI sessions from any MCP agent harness. | Local · stdio |
| AsyntheticGround truth for AI coding agents: what breaks between library versions and how to fix it. | Remote & Local · HTTP, SSE, stdioLive check: ✗ no handshake |
| Atag MCPATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers. | Local · stdio |
| Atest MCP ServerAuto-download & launch https://github.com/LinuxSuRen/atest-mcp-server. | Local · stdio |
| Athena ProtocolAI tech lead for coding agents with validation and impact analysis. | Local · stdio |
| Atlarium Habitat Database MCPStructured habitat data and advisory tools for aquariums, marine tanks, terrariums and paludariums. | Remote · HTTPLive check: ✓ handshake |
| Atlas Data ExchangeInfrastructure and hazard intelligence with provenance, spatial confidence and quality contracts. | Remote · HTTPLive check: ✓ handshake |