Stata MCP Server (macOS)

Created By
mkprevoa year ago
MCP server for stata do file
Overview

what is Stata MCP Server?

Stata MCP Server is a Model Context Protocol (MCP) server designed for managing and executing Stata .do files, integrating seamlessly with Claude Desktop.

how to use Stata MCP Server?

To use the Stata MCP Server, restart Claude Desktop, enable the server, and use commands to manage and run .do files.

key features of Stata MCP Server?

  • File management for .do files (list, read, write)
  • Edit specific sections of .do files (add variables, analysis code)
  • Automation features to generate and run .do files
  • Backup system for automatic file backups

use cases of Stata MCP Server?

  1. Managing and executing statistical analysis scripts in Stata.
  2. Automating the creation of .do file templates for data analysis.
  3. Running specific lines of code from .do files for testing purposes.

FAQ from Stata MCP Server?

  • Can I run Stata .do files on macOS?

Yes! The Stata MCP Server is specifically designed for macOS users.

  • How do I troubleshoot if Stata fails to run?

Check the Stata path and ensure your Stata license is valid.

  • Is there a backup system in place?

Yes! The server creates automatic backups of .do files when modified.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mkprevo
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

29 minutes ago