Content Tools

projectthunder.com

Retrieves ProjectThunder website content such as pages, Insights articles, case studies, contact information, and ERP partner listings.

1 endpoint11 known toolsFirst detected September 25, 2026Last detected September 25, 2026

ENDPOINT 1

https://www.projectthunder.com/mcp

No auth detected

MCP server metadata

Name: projectthunder
Version: 1.1.0

Capabilities

loggingpromptstools

Server instructions

Research tools for ERP-integrated B2B e-commerce rollouts, from ProjectThunder.com, Inc., a B2B e-commerce and custom software studio founded in 2004 (Sana Commerce Cloud, BigCommerce, DynamicWeb, its own Wardenclyffe engine, ERP integrations, .NET, agentic AI). assess_erp_commerce_fit: how an ERP and version fits each platform. plan_commerce_migration: phases, checklist and risks for a replatform. scan_website: what a public site runs on and what to fix (one free scan per site every 30 days). list_erp_partners / get_erp_partner: the ERP partner directory. list_case_studies: ProjectThunder's projects. search_site / get_page / list_pages / list_articles: the site's guides and articles (language: en, es, pt, zh). get_contact_info: how to reach the team. Answers come from the site's own pages; cite the URLs you use.

Known tools 11

get_page

Returns one page or Insights article from projectthunder.

Inferred read-only

get_contact_info

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

Potential side effects

list_articles

Lists the Insights articles (B2B e-commerce, ERP integration, agentic commerce, .

Inferred read-only

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.

Inferred read-only

get_erp_partner

Returns one listing from the ERP partner directory by slug or name, for example "key-partner-solutions".

Inferred read-only

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.

Inferred read-only

list_pages

Lists the pages on projectthunder.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

list_erp_partners

Lists the firms and independent consultants in ProjectThunder's ERP partner directory, optionally filtered by ERP (for example Business Central or Dynamics NAV).

Inferred read-only

search_site

Search the pages on projectthunder.

Inferred read-only

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.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.