Marketing

thrivepro.in

An MCP server that provides information about Thrive Pro's services, company details, FAQ, blog posts, and allows booking a call.

1 endpoint6 known toolsFirst detected September 24, 2026Last detected September 24, 2026

ENDPOINT 1

https://www.thrivepro.in/api/mcp

No auth detected

MCP server metadata

Name: thrive-pro
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

Thrive Pro: websites, BotX (WhatsApp + web AI agent), AI readiness, and e-commerce for businesses in Chennai, India. Use get_company_info, get_services, and get_faq to answer questions; use get_blog_posts and get_blog_post for blog content and citations; use book_a_call to submit a lead.

Known tools 6

get_company_info

Returns Thrive Pro's identity, location, how-we-work steps, why-us points, pricing model, and proof of work.

Inferred read-only

get_services

Returns Thrive Pro's service list (BotX, Websites, AI Readiness, E-commerce).

Inferred read-only

get_faq

Returns Thrive Pro's FAQ (Meta ban risk, data safety, pricing, existing-website compatibility, technical-knowledge requirement).

Inferred read-only

book_a_call

Submits a lead to Thrive Pro requesting a call back.

Inferred read-only

get_blog_posts

Returns Thrive Pro's blog post list (title, url, excerpt, publishedAt, categories).

Potential side effects

get_blog_post

Returns one Thrive Pro blog post's full content as markdown, by slug.

Potential side effects

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.thrive-pro]
url = "https://www.thrivepro.in/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "thrive-pro": {
      "type": "http",
      "url": "https://www.thrivepro.in/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: thrive-pro
Remote MCP URL: https://www.thrivepro.in/api/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": {
    "thrive-pro": {
      "url": "https://www.thrivepro.in/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "thrive-pro": {
      "type": "http",
      "url": "https://www.thrivepro.in/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "thrive-pro",
  "transport": "streamable-http",
  "url": "https://www.thrivepro.in/api/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.