Agent Native Analytics vs Wellness Project

A side-by-side look at the Agent Native Analytics and Wellness Project MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Agent Native Analytics logoAgent Native AnalyticsDeveloper Tools · Local subprocess (stdio)Agent-Native Amplitude/Mixpanel - connect data sources, prompt for charts52GoodAuth: not declaredWellness Project logoWellness ProjectDeveloper Tools · Remote HTTP/SSEHosted MCP server connecting Apple Health, Fitbit, Oura & Health Connect to Claude and ChatGPT.43FairAuth: oauth 2.0

Verdict: choose Agent Native Analytics for developer tools work as a local process; choose Wellness Project for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Agent Native Analytics logoChoose Agent Native Analytics when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore Agent Native Analytics

Wellness Project logoChoose Wellness Project when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore Wellness Project

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAgent Native Analytics logoAgent Native AnalyticsWellness Project logoWellness Project
CategoryDeveloper ToolsDeveloper Tools
Quality signal52/100 · Good43/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredOAuth 2.0
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars7,4602
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Agent Native Analytics tools

No tool names declared yet. Check the project README from the listing page.

Wellness Project tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Agent Native Analytics

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "agent-native-analytics": {
      "command": "npx",
      "args": [
        "--yes",
        "@agent-native/core@latest"
      ]
    }
  }
}

Wellness Project

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "wellness-project": {
      "url": "https://wellnessproject.ai/api/mcp"
    }
  }
}

Frequently asked questions

Agent Native Analytics is categorized under Developer Tools and uses a local stdio subprocess. Wellness Project belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Agent Native Analytics for developer tools work and Wellness Project for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Agent Native Analytics is listed as free. Wellness Project has no declared pricing — check the project's own site. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add agent-native-analytics and wellness-project as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Agent Native Analytics has a quality signal of 52/100 (Good) with 1 views, 0 installs and 7,460 GitHub stars. Wellness Project has 43/100 (Fair) with 1 views, 0 installs and 2 GitHub stars.