home / mcp / moz da pa1 mcp server

Moz Da Pa1 MCP Server

Provides access to Moz Da Pa1 data via a stdio-based MCP server with API key authentication.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "bach-ai-tools-bachai-moz-da-pa1": {
      "command": "python",
      "args": [
        "server.py"
      ],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

This MCP server lets you access the Moz Da Pa1 API through a lightweight bridge you can run locally or via the EMCP platform. It exposes a simple stdio-based interface so your applications can query Moz Da Pa1 data like Domain Authority, Page Authority, external links, and Spam Score with a clean integration path.

How to use

You will use an MCP client to connect to this server. Start the server locally or through an MCP platform, then point your client to the local stdio entry or to the platform-configured path. Use the API key you obtain to authenticate requests. For the quickest setup, choose the uvx-based run or the direct Python run, then query the available endpoints to fetch Moz Da Pa1 metrics.

How to install

Prerequisites: Python and pip must be installed on your system. If you plan to use uvx for running MCPs, ensure uvx is available (it can install automatically when you run the uvx command). Then you can install the Moz Da Pa1 MCP package.

pip install bach-moz_da_pa1

# Optional: install in editable mode if you are developing against the source
pip install -e .

# If you want to validate the package is installed, you can run:
bach_moz_da_pa1 --help

# Alternatively, run via uvx (recommended for seamless startup):
uvx --from bach-moz_da_pa1 bach_moz_da_pa1

# Or run in development mode directly with Python:
python server.py

# After installation, you can also run as a command from the shell:
bach_moz_da_pa1

Configuration and usage details

API requests require authentication. Set your API key in the environment before starting the server.

export API_KEY="your_api_key_here"

In Cursor and Claude Desktop

If you use Cursor MCP or Claude Desktop, add the following MCP server configuration to your client setup to run the Moz Da Pa1 MCP via uvx with the API key.

{
  "mcpServers": {
    "bach-moz_da_pa1": {
      "command": "uvx",
      "args": ["--from", "bach-moz_da_pa1", "bach_moz_da_pa1"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

Recommendations for production use

For production workloads, use the uvx-based run for automatic installation and startup, and store your API keys securely in environment variables. If you prefer direct development, you can start the server with Python, but ensure you supply the API key through the environment for every run.

Security and troubleshooting

Never expose your API key in client-side code or logs. Use secure storage for environment variables and rotate keys periodically. If you encounter authentication errors, verify that the API_KEY variable is set in the environment where the MCP server runs.

End points and tools

The MCP server exposes the getdapa tool to retrieve Moz Da Pa1-related data, including Domain Authority, Page Authority, and external link metrics.

Available tools

getdapa

Fetches Moz Da Pa1 data such as Domain Authority, Page Authority, external nofollow URLs, external URLs, and Spam Score via the /v1/getDaPa endpoint.