Moesif MCP Server

The Moesif Model Context Protocol (MCP) server lets AI assistants like Claude Code query and act on your Moesif data using natural language. Instead of navigating dashboards in Moesif Web Portal UI, you can ask Claude to explore your API traffic, build charts, and manage dashboards on your behalf.

Once you connect to Moesif MCP, you can use tools like Claude for various tasks, for example:

Explore your API events and search across fields for information about endpoints, status codes, and latency.
Create, preview, and save workspaces like time series, bar charts, and funnels.
List, view, and update your dashboards.

This guide walks through adding the Moesif MCP server to Claude Code and trying it out with a few sample prompts.

Prerequisites

Node.js 18 or later.
The Claude Code CLI. Follow the official instructions to install it and confirm it’s working:
```
claude --version
```
See Cladue Code’s setup documentation if you run into issues installing Claude Code on your platform.
A Moesif account with access to the organization and application you want to query.

1. Add the Moesif MCP server

Run the following command to register Moesif as an MCP server in Claude Code:

claude mcp add --transport http moesif https://api.moesif.com/mcp

2. Authenticate with OAuth

claude mcp login moesif

This opens a browser window. Sign in to Moesif. Then pick the organization and application you want Claude to use. You must also specify an access level, either read-only or read and write. Finally, approve the request to finish connecting.

Verify the connection:

claude mcp list        # moesif → ✓ connected

Start Claude Code with claude, then run /mcp inside a session to see the Moesif tools that are available.

Tip: If your session expires, reconnect with claude mcp login moesif. To disconnect Moesif entirely and clear the stored credentials, run claude mcp logout moesif.

To confirm everything’s working, start a claude session and ask the following:

Run moesif whoami and tell me which org and app I’m connected to.

3. Try it out

Once connected, type prompts like these in a claude session.

Explore your data

What API traffic did we get in the last 24 hours? Break it down by endpoint and status code.
Which fields are available on my events for filtering? Show me the most useful ones.

Create a workspace chart

Create a workspace chart showing 4xx and 5xx errors per day over the last 30 days, grouped by status code. Name it “Error Rate by Status”.
Create a workspace showing the top 10 endpoints by request volume for the last 7 days, as a bar chart.
Preview a chart of P95 latency by endpoint over the last 7 days before saving it, then save it as “Latency p95 by Endpoint”.

Work with dashboards

List my dashboards, then add the “Error Rate by Status” workspace to the API Health dashboard.
Show me the charts on my API Health dashboard and explain what each one measures.

Access levels and permissions

The access level you choose during authentication controls what Claude can do through the Moesif MCP server:

Read-only: Claude can explore events and view existing workspaces and dashboards, but can’t create or modify anything.
Read and write: Claude can also create and save new workspaces, and create or update dashboards, in addition to everything allowed by read-only access.

You can change the organization, application, or access level at any time by running claude mcp logout moesif followed by claude mcp login moesif again.

Troubleshooting

claude mcp list doesn’t show Moesif as connected: Sessions can expire periodically. So run claude mcp login moesif to reauthenticate.
Claude can’t see the organization or application you expect: Confirm your Moesif account has access to that organization and application. Then log out and back in. See Apps and Team for managing access.
Claude says it can’t create or save a workspace: You likely authenticated with read-only access. Log out and back in, selecting read and write access when prompted.