
Agentmark Ai
io.github.agentmark-aiPublished by GitHub account agentmark-aiv0.4.2Updated Oct 24, 2026
Inspect AgentMark traces and drive AgentMark Cloud: apps, experiments, metrics, deployments.
Overview
Lets an assistant inspect AgentMark traces and drive AgentMark Cloud apps, experiments, metrics and deployments.
- What you can do
- This server lets an assistant inspect AgentMark traces and drive AgentMark Cloud, covering apps, experiments, metrics and deployments. It runs as a local stdio process that bridges the assistant to the AgentMark platform.
- When to use it
- Use it when you work with the AgentMark platform and want the assistant to inspect traces, experiments, metrics or deployment state directly instead of switching to the web interface. If you have no AgentMark account or do not need cloud platform operations, there is little reason to add it.
- Requirements
- Runs locally as the npm package @agentmark-ai/mcp-server over stdio, so a Node.js environment is needed. An AgentMark account is required; authenticate with an app-scoped API key in the AGENTMARK_API_KEY environment variable, or use the session bearer written by agentmark login. AGENTMARK_API_URL can set the gateway base URL. Desktop only.
Installation
In SourceWeft
- Open Agentmark Ai in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.4.2LatestSep 16, 2026
Score
25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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.