DevMeter Now Has an MCP Server for Agent Access

DevMeter now exposes a real Model Context Protocol (MCP) server, which means AI tools and MCP-aware editors can discover DevMeter directly instead of relying on manual setup or custom integrations.

This is a big step for the project because it makes DevMeter easier to connect to from modern agent workflows, including VS Code Copilot and other MCP-compatible tools.

What the MCP Server Can Do

The server currently exposes live tools for:

It also exposes resources so agents can discover documentation and other useful context without leaving the protocol.

Why This Matters

This gives DevMeter a more natural integration path for agentic workflows. Instead of hard-coding knowledge about the product, an MCP-capable tool can ask the server what is available and call the right action directly.

That means:

What Users Can Try

If you are using a compatible editor or agent, you can now connect it to the DevMeter MCP endpoint and ask things like:

How to Connect in VS Code

You can connect in under two minutes:

1. Open the workspace where you want MCP enabled.

2. Create or update the file: .vscode/mcp.json

3. Add DevMeter as an HTTP MCP server with URL: https://devmeter-v2.zaidcode.me/api/mcp and type: http

4. Reload VS Code so MCP servers reconnect.

5. Ask your agent to call DevMeter tools, for example:

If you are testing locally, use this URL while your app is running: http://localhost:3000/api/mcp

Built for the Real World

This is not just a demo stub. The MCP server is wired into the live DevMeter app, so the tools return real platform data from the production environment.

We'll keep expanding the surface area over time, but the important milestone is here: **DevMeter is now MCP-enabled.**