INDIVIDUAL MCP TOOL

get_contact_info

ProjectThunder's phone number, email, contact page, mailing address, where the team works and the topics the contact form covers.

projectthunder.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://www.projectthunder.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_contact_info and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

A tool name or description suggests sending messages.

Parent server

projectthunder.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.projectthunder]
url = "https://www.projectthunder.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "projectthunder": {
      "type": "http",
      "url": "https://www.projectthunder.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: projectthunder
Remote MCP URL: https://www.projectthunder.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "projectthunder": {
      "url": "https://www.projectthunder.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "projectthunder": {
      "type": "http",
      "url": "https://www.projectthunder.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "projectthunder",
  "transport": "streamable-http",
  "url": "https://www.projectthunder.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

get_page — Returns one page or Insights article from projectthunder.
list_articles — Lists the Insights articles (B2B e-commerce, ERP integration, agentic commerce, .
list_case_studies — Projects from ProjectThunder's portfolio: the client, the platform (Sana Commerce, BigCommerce, DynamicWeb, mobile, AI), the industry, the ERP where the site names it, and what was built.
get_erp_partner — Returns one listing from the ERP partner directory by slug or name, for example "key-partner-solutions".
plan_commerce_migration — A rollout plan for moving a B2B store from one platform to another around an ERP, from ProjectThunder's published method: the migration paths its pages cover, project phases, a pre-migration checklist, risks with mitigations, which integration pattern fits (real-time, middleware or batch), when each platform is the right target, and the ERP's own caveats when one is named.
list_pages — Lists the pages on projectthunder.
scan_website — Scans one public website with ProjectThunder's site scan: detects the commerce platform and technologies in use (public BuiltWith data plus the home page), then returns a plain-English summary, what is working, risks that may be costing customers, growth and modernization opportunities, SEO and security notes, AI opportunities, and 0-100 scores.
assess_erp_commerce_fit — For an ERP (and optionally a version and an e-commerce platform), returns how it integrates with Sana Commerce Cloud, BigCommerce, DynamicWeb or Wardenclyffe, version notes such as end-of-support dates, what to settle first, the guides that cover it, and implementation partners in ProjectThunder's ERP partner directory.