WeInc MCP Server

by umairalisadaqat Your server? Claim it

answering

WeInc is answering right now. Last checked 6 min ago. It exposes 7 tools.

Start, browse and manage your WeInc websites from your AI assistant.

Uptime history 91 days of history · worst day 93%

91 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

628 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 39

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 October 2026. No other catalogue keeps this.

7 Nov 12 tool descriptions were rewritten15 times that day create_client, create_website_from_template, find_templates and 9 more

7 Nov 10 tools disappeared create_client, create_project, get_analytics and 7 more

7 Nov a tool changed the parameters it asks for create_website_from_template

6 Nov 2 tools appeared create_website_from_template, publish_website

6 Nov 2 tool descriptions were rewritten create_website_from_template, start_website

6 Nov a tool changed the parameters it asks for create_website_from_template

30 Oct a tool description was rewritten create_project

30 Oct a tool changed the parameters it asks for create_project

19 Oct a tool description was rewritten update_project

14 Oct 5 tools appeared find_templates, my_websites, request_change and 2 more

and 3 more, back to 14 October 2026

WeInc missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add weinc --transport http https://my.we.inc/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://my.we.inc/api/mcp

~/.codex/config.toml

[mcp_servers.weinc]
url = "https://my.we.inc/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "weinc": {
      "url": "https://my.we.inc/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "weinc": {
      "type": "http",
      "url": "https://my.we.inc/api/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

website

create_website_from_template

Instantly make a finished website in the person's own WeInc account from one of WeInc's ready-made designs, personalised with their business name and details. Takes about a second and returns the editor link where they can see it, change anything and publish. A few general sections (such as service highlights) are placeholder text for the person to edit. Use this when the person wants a WeInc website made from a ready-made design. Call it right away with what they have told you; the business name is enough, so do not ask follow-up questions first (they can change anything afterwards). Pass `template_id` from find_templates, or leave it out and give `business_type` and/or `description` so the best design is picked. Only pass details the person actually gave; never invent a phone number, email or city. For a custom AI-designed site use start_website instead.It is not published; offer publish_website afterwards if the person wants it live.

website_details

Details of one of the person's own websites: name, whether it is published, live URL, custom domains with status, last published time and editor link.

publish

publish_website

Put one of the person's own WeInc websites live on the internet at its weinc.app address (or its connected domain), exactly like pressing Publish in the editor. Usually takes 15-45 seconds and returns the live link; if it takes longer it answers 'publishing' and website_details gives the live link shortly after. The site becomes public, so ask the person before calling this. The account's plan sets how many sites can be live at once; a refusal explains why.

request

request_change

Prepare a change to one of the person's own websites. Returns an editor link that opens their site with the instruction already typed in the WeInc chat box; it is NOT sent until they press send. The instruction should say what to change, where, and the exact new text.

start

start_website

Only for when the person explicitly asks for a custom, from-scratch, AI-designed WeInc website. It does NOT make a site: it returns a link, and the AI build starts only after the person confirms in their browser. For any other request for a WeInc website ("make me a website for my bakery"), use create_website_from_template instead: it makes the finished site immediately. Put everything you know into `brief`: business name, what they do, location, services, audience, tone, pages wanted, contact details. Optionally pass `template_id` from find_templates. The build starts only after the person confirms on that page.

templates

find_templates

Search WeInc's website templates by keywords (e.g. 'restaurant', 'portfolio', 'online store') and/or category. Returns id, name, description, category, features and a start link. Pass a chosen id to create_website_from_template as template_id.

websites

my_websites

List the signed-in person's own WeInc websites, newest activity first: name, live URL if published, editor link and last updated time. Use the id with website_details or request_change.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

create_client

removed 7 Nov 2026

create_project

removed 7 Nov 2026

get_analytics

removed 7 Nov 2026

get_preview_urls

removed 7 Nov 2026

get_project

removed 7 Nov 2026

list_clients

removed 7 Nov 2026

list_plans

removed 7 Nov 2026

list_projects

removed 7 Nov 2026

list_templates

removed 7 Nov 2026

update_project

removed 7 Nov 2026

Endpoints

URL	Transport	State	Latency	Checked
https://my.we.inc/api/mcp	streamable-http	answering	446 ms	6 min ago

Alternatives to WeInc

same job, measured the same way

Mailiy

by mailiy

Form backend: manage websites, forms, submissions, files and webhooks from your AI assistant.

answering

Vidalytics

by vidalytics

Manage your Vidalytics videos and analytics from your AI assistant.

answering

Squish

by squish

Manage your Squish domains, DNS, hosting, backups and site files from your AI assistant.

answering

MCP Advisor

by stucchi

Browse, search, and discover MCP servers from your AI assistant

143 installs/wk local only

Ybug

by ybug

Read, filter and triage Ybug website feedback and bug reports from your AI assistant

answering

Replo

by replohq

Research competitors and build, edit, and manage ecommerce sites from your AI assistant.

96 tools answering

Moxt Workspace

by moxt

Browse and manage files in your Moxt AI workspace from any MCP client.

answering

MeisterTask

by meistertask

Create and manage MeisterTask projects, tasks, and notes from your AI assistant.

answering

WeInc — questions

Answers built from our own checks of this server.

What can WeInc do?

It exposes 7 tools, read directly from the server on our last check. Among them: create_website_from_template, find_templates, my_websites, publish_website, request_change, start_website and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is WeInc working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 628 ms. The bar chart above shows every period we have measured.

Did WeInc ever remove tools?

Yes. create_client, create_project, get_analytics, get_preview_urls and 6 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

How do I connect WeInc?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does WeInc need an API key?

No. WeInc completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is WeInc?

It answers our handshake in 628 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.