
Plan a software project, check website speed, find Pulore case studies, get a booking link.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Use this when someone wants to know how fast a public web page is, why it's slow, how it does on Core Web Vitals or Lighthouse, or what to fix to speed it up. Runs Google PageSpeed Insights (Lighthouse) and returns performance, accessibility, best-practices and SEO scores, lab measurements, real-user Core Web Vitals when Google has them, and the fixes with the biggest estimated impact. The address is sent to Google, which loads the page. The tool does not edit the target website or submit forms. It only works on public pages, not local sites, pages behind a login or addresses that contain a password or token. An audit takes about 20 to 40 seconds, and the same page's result is reused for up to 12 hours. Don't use it to check whether a site is up, for security scans or for keyword research.
The public page to audit, for example example.com or https://example.com/pricing. No passwords, tokens or private links.
Test as a phone (the default, and what Google ranks on) or as a desktop.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http app-planner https://pulore.com/mcp
Use this when someone wants to know how fast a public web page is, why it's slow, how it does on Core Web Vitals or Lighthouse, or what to fix to speed it up. Runs Google PageSpeed Insights (Lighthouse) and returns performance, accessibility, best-practices and SEO scores, lab measurements, real-user Core Web Vitals when Google has them, and the fixes with the biggest estimated impact. The address is sent to Google, which loads the page. The tool does not edit the target website or submit forms. It only works on public pages, not local sites, pages behind a login or addresses that contain a password or token. An audit takes about 20 to 40 seconds, and the same page's result is reused for up to 12 hours. Don't use it to check whether a site is up, for security scans or for keyword research.
| Argument | Type | Description |
|---|---|---|
| url* | string | The public page to audit, for example example.com or https://example.com/pricing. No passwords, tokens or private links. |
| device | string | Test as a phone (the default, and what Google ranks on) or as a desktop. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"maxLength": 2048,
"minLength": 3,
"description": "The public page to audit, for example example.com or https://example.com/pricing. No passwords, tokens or private links."
},
"device": {
"enum": [
"mobile",
"desktop"
],
"type": "string",
"default": "mobile",
"description": "Test as a phone (the default, and what Google ranks on) or as a desktop."
}
}
}Use this only when someone asks about Pulore's own work or experience, for example whether Pulore has built something like their idea. Finds published Pulore case studies related to a topic, matching industry, platform, services and technology tags, and returns each project's summary and link, with timeline, team size and results where the case study publishes them. Searches the case-study files bundled with this server; it does not browse or modify external sites. Returns nothing when no project matches. Don't use it to find examples of other companies' products.
| Argument | Type | Description |
|---|---|---|
| query* | string | What the project is about, for example 'health app with HIPAA' or 'Shopify storefront'. Topic words only, no personal details. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"maxLength": 200,
"minLength": 2,
"description": "What the project is about, for example 'health app with HIPAA' or 'Shopify storefront'. Topic words only, no personal details."
}
}
}Use this only when someone asks to talk to Pulore or book a call with them. Builds a link locally to Pulore's fixed Cal.com page for a 30-minute intro call, with the person's name, email and a short note filled in when given. This tool makes no request to Cal.com and does not create or reserve a booking. The person opens the link, picks a time and confirms on Cal.com themselves.
| Argument | Type | Description |
|---|---|---|
| name | string | The person's name, to fill in the booking form. |
| note | string | A one or two sentence note about the project for the call. Never include payment details, ID numbers, passwords, keys or health records. |
| string | Their email, to fill in the booking form. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"description": "The person's name, to fill in the booking form."
},
"note": {
"type": "string",
"maxLength": 500,
"description": "A one or two sentence note about the project for the call. Never include payment details, ID numbers, passwords, keys or health records."
},
"email": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
"maxLength": 200,
"description": "Their email, to fill in the booking form."
}
}
}Use this when someone wants to know what it would take to build a software product, such as an app, website, SaaS, marketplace, internal tool, AI feature or MVP: how long it would take, what it would cost, what team or tech stack it needs, or a build plan or estimate for their idea. Returns a rough plan with effort ranges for each feature, the team, a timeline range, phases, a suggested stack and a budget (the hours priced at $100 to $150 an hour). The ranges reflect how Pulore builds today, with managed services such as Clerk and Stripe where they fit and AI-assisted development. The plan is calculated locally from fixed estimation tables; this tool does not save a project or call an external service. Map the idea to the closest features in the list and say in your reply what doesn't fit. Results are planning ranges, not a quote. Don't use it for projects that aren't software (like renovations, events or business plans), for task or project management, or to write code.
| Argument | Type | Description |
|---|---|---|
| features* | array | The features it needs. Choose from: accounts (Sign-up, login and user accounts), teams_roles (Teams, roles and permissions), payments (Payments and subscriptions), marketplace (Two-sided marketplace with payouts), admin_panel (Admin panel for your team), dashboards (Analytics dashboards and reports), messaging (Real-time chat or messaging), notifications (Email, push and in-app notifications), search (Search and filters), media_uploads (File, photo and video uploads), maps (Maps and location), booking (Scheduling and bookings), ecommerce (Product catalog, cart and checkout), headless_shopify (Headless Shopify storefront), cms (Content your team edits in a CMS), ai_assistant (AI assistant or chat over your own data), ai_documents (AI document processing (reading, extracting, summarizing)), ai_voice (AI voice agent), integrations (Integrations with a few third-party APIs), offline (Offline mode and sync), multi_tenant (Separate accounts for business customers (multi-tenant)), background_jobs (Data pipelines and background jobs), public_api (A public API for your customers), three_d (3D or AR experiences). For example, subscriptions are payments, a chatbot over their docs is ai_assistant, and a dashboard for their own staff is admin_panel. |
Use this only when the person has explicitly asked to contact Pulore or send Pulore their project. Sends an external email through Resend to Pulore's fixed inbox, [email protected], so the team can reply to the person directly. This sends a message outside ChatGPT and cannot be recalled by this tool. First show them the recipient and every field you'll send, and call this only after they approve. The email contains only these fields, never the conversation. A brief identical to one sent in the last day isn't sent again, and each email address can send a few briefs a day.
| Argument | Type | Description |
|---|---|---|
| name* | string | The person's name. |
| email* | string | The email address Pulore should reply to. |
| budget | string | Their budget range, if they chose to share it. |
| company | string | Their company or role, if they gave one. |
| timeline | string | When they hope to start or launch, if they said. |
| project_brief* | string | What they want to build and what they want from Pulore, exactly as they approved it. Product requirements only. Never include payment details, ID numbers, passwords, keys or health records. |
We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 4, 2026.
| platforms* | string | Where it runs: web, mobile (iOS and Android) or web_and_mobile. |
| compliance | array | Compliance it must meet, if any: hipaa (HIPAA (US health data)), soc2 (SOC 2 readiness), gdpr (GDPR). |
| needs_design* | boolean | True if they don't have designs yet and need design work. If they haven't said, assume true and mention the assumption. |
| project_summary | string | One short sentence on what they want to build, used as the plan's title. Product details only. Never include payment details, ID numbers, passwords, keys or health records. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"platforms",
"features",
"needs_design"
],
"properties": {
"features": {
"type": "array",
"items": {
"enum": [
"accounts",
"teams_roles",
"payments",
"marketplace",
"admin_panel",
"dashboards",
"messaging",
"notifications",
"search",
"media_uploads",
"maps",
"booking",
"ecommerce",
"headless_shopify",
"cms",
"ai_assistant",
"ai_documents",
"ai_voice",
"integrations",
"offline",
"multi_tenant",
"background_jobs",
"public_api",
"three_d"
],
"type": "string"
},
"maxItems": 20,
"minItems": 1,
"description": "The features it needs. Choose from: accounts (Sign-up, login and user accounts), teams_roles (Teams, roles and permissions), payments (Payments and subscriptions), marketplace (Two-sided marketplace with payouts), admin_panel (Admin panel for your team), dashboards (Analytics dashboards and reports), messaging (Real-time chat or messaging), notifications (Email, push and in-app notifications), search (Search and filters), media_uploads (File, photo and video uploads), maps (Maps and location), booking (Scheduling and bookings), ecommerce (Product catalog, cart and checkout), headless_shopify (Headless Shopify storefront), cms (Content your team edits in a CMS), ai_assistant (AI assistant or chat over your own data), ai_documents (AI document processing (reading, extracting, summarizing)), ai_voice (AI voice agent), integrations (Integrations with a few third-party APIs), offline (Offline mode and sync), multi_tenant (Separate accounts for business customers (multi-tenant)), background_jobs (Data pipelines and background jobs), public_api (A public API for your customers), three_d (3D or AR experiences). For example, subscriptions are payments, a chatbot over their docs is ai_assistant, and a dashboard for their own staff is admin_panel."
},
"platforms": {
"enum": [
"web",
"mobile",
"web_and_mobile"
],
"type": "string",
"description": "Where it runs: web, mobile (iOS and Android) or web_and_mobile."
},
"compliance": {
"type": "array",
"items": {
"enum": [
"hipaa",
"soc2",
"gdpr"
],
"type": "string"
},
"default": [],
"maxItems": 3,
"description": "Compliance it must meet, if any: hipaa (HIPAA (US health data)), soc2 (SOC 2 readiness), gdpr (GDPR)."
},
"needs_design": {
"type": "boolean",
"description": "True if they don't have designs yet and need design work. If they haven't said, assume true and mention the assumption."
},
"project_summary": {
"type": "string",
"maxLength": 300,
"description": "One short sentence on what they want to build, used as the plan's title. Product details only. Never include payment details, ID numbers, passwords, keys or health records."
}
}
}{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"name",
"email",
"project_brief"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "The person's name."
},
"email": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
"maxLength": 200,
"description": "The email address Pulore should reply to."
},
"budget": {
"type": "string",
"maxLength": 100,
"description": "Their budget range, if they chose to share it."
},
"company": {
"type": "string",
"maxLength": 120,
"description": "Their company or role, if they gave one."
},
"timeline": {
"type": "string",
"maxLength": 100,
"description": "When they hope to start or launch, if they said."
},
"project_brief": {
"type": "string",
"maxLength": 3000,
"minLength": 10,
"description": "What they want to build and what they want from Pulore, exactly as they approved it. Product requirements only. Never include payment details, ID numbers, passwords, keys or health records."
}
}
}