Developer · Remote MCP server
artifacta.io
Artifact store for AI agents. Hosted OAuth at mcp.artifacta.io/mcp; local stdio via npm/PyPI.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.artifacta/mcp- Version
- 1.0.5
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm, PyPI
- Published
- 2026-06-30
- Updated
- 2026-06-30
- Publisher
- io.artifacta
- Repository
- github.com/SagaPeak/artifacta-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.artifacta.io/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @artifacta-mcp/mcp | 1.0.4 | stdio |
| PyPI | artifacta-mcp | 1.0.4 | stdio |
How to connect artifacta.io
artifacta.io is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.artifacta.io/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: @artifacta-mcp/mcp version 1.0.4. 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 @artifacta-mcp/mcp@1.0.4. It reads the environment variable ARTIFACTA_API_KEY (required, secret); set it in the client's configuration for this server.
It can also run locally from a Python package published to PyPI: artifacta-mcp version 1.0.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx artifacta-mcp. It reads the environment variable ARTIFACTA_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@artifacta-mcp/mcp@1.0.4"
],
"env": {
"ARTIFACTA_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. 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 |
|---|---|
| Arm MCP ServerOfficial Arm MCP server for code migration, optimization, and Arm architecture guidance. | Local · stdio |
| ARNOThe IDE for agents: read by symbol, edit against a revision, validate with your own build, revert. | Local · stdio |
| ArrowayShared memory for people and their AIs: read what was decided before acting, log what was done. | Remote · HTTP |
| Artifact Hub MCPHelm charts and cloud native packages from Artifact Hub. No key required. | Local · stdio |
| Artillery MCPMCP server for Artillery 2.x — full flags, Fargate, raw-text parser, project launcher (MIT) | Local · stdio |
| Aruba Central MCPMCP server for Aruba Central: expose AP, switch, and client status to AI assistants. | Local · stdio |
| ArxivArXiv MCP — preprint server search (free, no auth) | Remote · HTTP |
| Asana MCP ServerChange Asana without opening Asana — custom fields, sections, start dates, rich notes, bulk. PAT. | Local · stdio |