Inspect AgentMark traces and drive AgentMark Cloud: apps, experiments, metrics, deployments.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-agentmark-ai-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
AgentMark is an open-source platform for building reliable AI agents. Define prompts in Markdown, run them with the SDK you already use, evaluate against datasets locally or in CI, and trace every call with OpenTelemetry.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops / analytics
MCP server for using the GitLab API
⚡ A Simple / Speedy / Secure Link Shortener with Analytics, 100% run on Cloudflare.
MCP Server for GCP environment for interacting with various Observability APIs.
All-in-One Sandbox for AI Agents that combines Browser, Shell, File, MCP and VSCode Server in a single Docker container.
MCP Security Weekly
Get CVE alerts and security updates for io.github.agentmark-ai/mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Git-native AI agents.
Prompts and datasets in your repo. Evals in CI. Traces in your OTEL backend.
AgentMark is an open-source platform for building reliable AI agents. Define prompts in Markdown, run them with the SDK you already use, evaluate against datasets locally or in CI, and trace every call with OpenTelemetry.
.prompt.mdx files with type-safe inputs, tools, structured outputs, conditionals, loops, and reusable components. They live in your repo, get reviewed in PRs, and roll back with git revert.Requires: Node.js 18 or newer.
# Scaffold a new project (interactive: picks your language)
npm create agentmark@latest my-agents
cd my-agents
# Start the dev server (API + trace UI + hot reload)
agentmark dev
# Run a single prompt
agentmark run-prompt agentmark/my-prompt.prompt.mdx
# Run an experiment against a dataset
agentmark run-experiment agentmark/my-prompt.prompt.mdx
About five minutes from npm create to a traced prompt running locally (assuming you have an LLM API key set up).
---
name: customer-support-agent
text_config:
model_name: anthropic/claude-sonnet-4-20250514
max_calls: 2
tools:
- search_knowledgebase
test_settings:
props:
customer_question: "How long does shipping take?"
input_schema:
type: object
properties:
customer_question:
type: string
required: [customer_question]
---
<System>
You are a helpful customer service agent. Use the search_knowledgebase tool
when customers ask about shipping, warranty, or returns.
</System>
<User>{props.customer_question}</User>
The frontmatter declares which tools the prompt may call; the implementations live in your code, resolved where you call the model. See Tools and agents.
Run it:
agentmark run-prompt customer-support.prompt.mdx
The prompt is version-controlled, type-checked, and traced. The same file works with any SDK — the Vercel AI SDK, the raw OpenAI or Anthropic client, Pydantic AI, or your own bespoke client. AgentMark renders the prompt to a neutral { messages, ...config } shape; your SDK makes the call.
Most AI tooling treats the dashboard as the primary workspace. Prompts are rows in a database. Edits happen in a b