75 Tools · Model Context Protocol Server for AI Agents

Connect Claude, Cursor, and any MCP-compatible AI agent directly to DYNO Mapper. Manage projects, run accessibility audits, analyze website inventory, monitor keyword visibility, and surface SEO issues — all through natural conversation, without leaving your AI client.

Package: @dynomapper/mcp-server · Transport: stdio · Runtime: Node.js

Quick Navigation

Quickstart · Architecture · User · Projects · Project Metadata · Custom Logins · V.A.C.Q. Score · Sitemap Items · Inventory · SEO Audit · Analytics · Comments · Visibility & Keywords · Accessibility (Web) · Accessibility (PDF) · Assignments · Workflow Examples · Configuration

What is MCP?

The Model Context Protocol is an open standard from Anthropic that lets AI agents securely connect to external tools and data sources. Instead of writing a custom integration for every AI client, you stand up one MCP server and it works with Claude Desktop, Cursor, Windsurf, and any other MCP-compatible host.

The DYNO Mapper MCP server translates AI tool calls into requests against the DYNO Mapper Public API, handling authentication, retries, and error recovery automatically. Your agent can plan a redesign, audit a client site for WCAG issues, surface SEO problems, or pull keyword rankings — all through natural language.

Quickstart

⚡ Get Connected in Under a Minute

1. Generate a Personal Access Token

Log in to DYNO Mapper and navigate to app.dynomapper.com/developer. In the Personal Access Tokens section, click Generate, name your token, and copy it somewhere safe.

Keep your Personal Access Tokens secure and never share them publicly or commit them to source control.

2. Add to Claude Desktop

Open Claude Desktop and edit your config file:

• macOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the DYNO Mapper server:

{
  "mcpServers": {
    "dynomapper": {
      "command": "npx",
      "args": ["-y", "@dynomapper/mcp-server"],
      "env": {
        "MCP_API_KEY": "your_personal_access_token_here"
      }
    }
  }
}

3. Restart Claude Desktop

That’s it. All 75 DYNO Mapper tools will appear in Claude Desktop. Try a prompt like:

“Pull my DYNO Mapper projects, then run a full SEO audit on the most recent one and summarize the top three issues.”

Cursor, Windsurf, and Other MCP Clients

The same server works in any MCP-compatible host. Add to the client’s MCP configuration with the same npx command and MCP_API_KEY environment variable:

{
  "mcpServers": {
    "dynomapper": {
      "command": "npx",
      "args": ["-y", "@dynomapper/mcp-server"],
      "env": {
        "MCP_API_KEY": "your_personal_access_token_here"
      }
    }
  }
}

Global Install (optional)

To skip the npx download on each launch:

npm install -g @dynomapper/mcp-server

Architecture

┌─────────────┐    stdio · JSON-RPC    ┌──────────────────────┐                ┌──────────────┐
│  AI Agent   │ ◄────────────────────► │   DYNO Mapper MCP    │ ◄────────────► │ DYNO Mapper  │
│  (Claude,   │                        │   @dynomapper/       │   REST / JSON  │  Public API  │
│   Cursor)   │                        │   mcp-server         │   Bearer PAT   │              │
└─────────────┘                        └──────────────────────┘                └──────┬───────┘
                                                                                      │
                                                                       ┌──────────────┼──────────────┐
                                                                       ▼              ▼              ▼
                                                                  Crawler &     Accessibility    Visibility
                                                                  Inventory       Engine         Tracking

The server is read-heavy by design — most tools fetch reports, audits, analytics, and rankings that DYNO Mapper has already computed from your scheduled crawls. A smaller set of tools creates, refreshes, or cancels project jobs and manages keyword groups.

Tool Reference

All 75 tools are grouped by module below.

User

Projects

Create projects from a live URL or from an uploaded text/XML file. Track job status, refresh, or cancel any project operation in flight.

Project Metadata

Custom Logins

Test and manage Custom System Authentication definitions for crawling private and SharePoint sites.

V.A.C.Q. Score

DYNO Mapper’s composite Visibility, Accessibility, and Content Quality score — a single dashboard metric for overall online presence health.

Sitemap Items

Inventory

Full content inventory: pages, links, and link occurrence tracking across the project.

SEO Audit

A full breakdown of on-page issues, with dedicated tools for each issue type so agents can pull just the slice they need.

Analytics

Project-level and page-level analytics, daily series, traffic sources, and events. Powered by your connected Google Analytics property.

Comments

Visibility & Keywords

Monitor search-engine visibility, manage keyword groups, and pull daily rankings by locale.

Accessibility (Web)

Run and review WCAG 2.1 / 2.2 accessibility audits. Pull results, history, scores, and granular item-level results.

Accessibility (PDF)

Assignments

Surface and triage content workflow assignments at the global or project level.

Workflow Examples

A few prompts to illustrate how tool calls chain together in practice.

Crawl a New Site and Summarize Issues

“Create a DYNO Mapper project for example.com, wait until the crawl is done, then give me the V.A.C.Q. score and the top SEO issues.”

create_project_from_url(url="https://example.com")
get_project_url_job_status(job_id=…)        # poll until complete
get_project_vacq_score(project_id=…)
get_audit_results(project_id=…)
get_audit_broken_links(project_id=…)
get_audit_missing_title(project_id=…)

Run a WCAG Audit on an Existing Project

“Run the accessibility checker on project 412 and show me the highest-severity problems grouped by guideline.”

run_accessibility_checker(project_id=412)
get_accessibility_score(project_id=412)
get_accessibility_report_groups(project_id=412)
get_accessibility_report_problems(project_id=412)

Track Keywords for a Client

“Add the keywords ‘enterprise CMS’, ‘headless CMS’, and ‘CMS migration’ to project 88, group them under ‘CMS Core’, and pull their current rankings.”

create_visibility_keyword_group(project_id=88, name="CMS Core")
create_visibility_keywords(project_id=88, keywords=[...])
update_visibility_keywords_group(project_id=88, keyword_id=…, group_id=…)
get_visibility_project_ranking(project_id=88)

Triage Outstanding Assignments

“Show me all open assignments across my projects with their totals, then drill into the oldest five.”

get_assignments_totals()
get_assignments(status="open", sort="created_at:asc", limit=5)
get_assignment_details(assignment_id=…)   # for each

Refresh a Project on Demand

“Re-crawl project 256 and let me know when it’s done.”

refresh_project_url(project_id=256)
get_project_url_job_status(job_id=…)      # poll until complete
get_audit_score(project_id=256)

Configuration

The MCP server is configured entirely through environment variables.

Where to Find Your Token

1. Log in to DYNO Mapper.
2. Go to https://app.dynomapper.com/developer.
3. Open the Personal Access Tokens section.
4. Click Generate, name your token, and copy it.

Treat your token like a password. Never commit it to source control, share it in screenshots, or paste it into untrusted clients. You can revoke and regenerate tokens at any time from the same page.

Resources

• npm: @dynomapper/mcp-server
• MCP Specification: modelcontextprotocol.io

Have questions, run into a bug, or want to request a tool? Open an issue on the package repository or contact the DYNO Mapper team.