INITE Agents

ai.initePublished by inite.aiOfficial publisherv0.1.0Updated Oct 30, 2026

Per-business MCP servers serving owner-confirmed facts: services, prices, hours, places, FAQ.

The publisher's own server: INITE Visibility

VerifiedStreamable HTTPWeb executableKnowledge & Memory Business & Commerce

Server details

Identifier: ai.inite/site-agents
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 22, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to inite.ai, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.inite%2Fsite-agents.svg)](https://sourceweft.com/mcp/ai.inite%2Fsite-agents?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Per-business remote MCP server that gives AI agents the owner-confirmed facts about a business: services, prices, hours, locations and FAQ.

What you can do: Read business facts, services, prices, hours, locations and FAQ through read-only tools
Serve the same confirmed facts to agents that read the site, alongside generated llms.txt, agent card and MCP server card files
Optionally publish articles written from measured search demand, only after each one is approved
Connect through WordPress, Next.js, a head snippet, Ghost or REST endpoints with signed webhooks
When to use it: For businesses that want AI assistants and browser agents to read accurate, owner-approved information about their services, prices and hours instead of guessing from a website. Useful when you already maintain your facts in the INITE cabinet and want them exposed to ChatGPT, Claude, Perplexity or in-browser agents.
Requirements: A remote endpoint at your business's own subdomain, reached over streamable HTTP. Facts must first be confirmed in the INITE cabinet, and a connector (WordPress plugin, Next.js package, head snippet, Ghost or REST with a site key) is needed to serve the files from your own domain. No authentication is declared for the MCP endpoint.

Before you install

The MCP endpoint is described as read-only, but the wider product writes to your site: it adds files, robots.txt lines, head tags and optionally articles, so review what each connector changes. The REST and webhook integrations use a site key; the README says it is only sent to the INITE origin. Articles are published only after approval, but that approval step is yours to enforce.

Installation

In SourceWeft

Open INITE Agents in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Follow the launch instructions in the repository.

README

INITE Agents

An AI agent that comes to your site gets the facts your business confirmed. That is the whole promise, and it is narrow on purpose. INITE Agents does not promise more recommendations or more traffic. It promises that ChatGPT, Claude, Perplexity or an agent in a visitor's browser gets your real services, prices, hours, locations and answers when it reads your site, and gets nothing you did not confirm.

You confirm the facts once in the INITE cabinet. INITE generates the files agents look for and runs an MCP server for your business. A connector on your site then serves everything from your own domain.

What agents get	Where
`llms.txt`	`/llms.txt`
A2A agent card	`/.well-known/agent-card.json`
MCP server card (`server.json` shape)	`/.well-known/mcp.json`
API catalog (RFC 9727)	`/.well-known/api-catalog`
`Content-Signal` line (contentsignals.org): search and answers yes, training no	`robots.txt`
WebMCP tools for an agent in the browser, `<link>` tags to the files, JSON-LD (Organization or LocalBusiness, FAQPage)	the page `<head>`
A remote MCP server with read-only tools: business facts, services, hours, locations, FAQ	`https://<your-slug>.inite.ai/mcp`
Optional: articles written from measured search demand, published only after you approve each one	your CMS

Connectors

Platform	Connector	Get it	Docs
WordPress	Plugin: root files, robots.txt, head, abilities for the WordPress MCP Adapter, articles	Releases · inite.ai zip · source	docs/wordpress.md
Next.js	npm package: two route files and one head component, plus the article queue	`@inite/site-agents` · source	docs/nextjs.md
Any site with a head-code box (Tilda, Squarespace, Wix, Webflow, Framer, Ghost, Shopify, Bitrix, Joomla, hand-made)	The snippet: one `<script>` tag, no key	the cabinet	docs/any-site.md
Ghost	INITE publishes approved articles through Ghost's Admin API; the snippet for the head	the cabinet	docs/ghost.md
Any stack	REST endpoints with a site key, and signed webhooks	the cabinet	docs/webhooks-and-rest.md · examples/
Webflow, Shopify, Framer, Wix, Notion, WordPress.com	Apps of their own are coming. Until then, the snippet connects all of these except Notion		docs/any-site.md

The full API reference is at https://inite.ai/en/mcp#site-api.

What INITE never does

Publishes a fact or a price you did not confirm.
Puts an article on your site that you did not approve.
Keeps a route claimed by a switched-off connector. Every connector switches off whole, and a feature that is off claims no URL and prints nothing.
Sends your site key anywhere but https://inite.ai. Connectors build every address from that origin and never follow a redirect with the key.
Lets an INITE outage take your site down. Connectors keep a copy and refresh it on a timer: hourly from WP-Cron in WordPress, at most once per period in Next.js, with a five-second limit. If INITE is down, the last good copy is served.

This repository

docs/: setup for each platform.
examples/: webhook receivers that verify the signature, in Node.js, PHP and Python, and a script that sends a signed test event.
Issues for every connector go here: open an issue.

The connectors' code lives in INITE's private monorepo. inite-agents-wordpress and site-agents are read-only mirrors of it, updated on every change. See CONTRIBUTING.md.

Security reports: [email protected] (SECURITY.md).

License

The docs and examples here are MIT licensed. The WordPress plugin is GPL-2.0-or-later. The Next.js package is MIT.

Source: README.md at commit 2d1f229

Tools

SourceWeft has not read this server's tools yet.

Version history

v0.1.0LatestOct 22, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Other Inite integrations

INITE Visibility

ai.initeOfficial publisher

Checks how AI answer engines read a website — crawler access, identity files, schema — and returns a visibility score, fix plan and competitor comparison.

Streamable HTTPWeb executable

Web Search & Scraping7 toolsOct 27, 2026

INITE Directory

ai.initeOfficial publisher

Remote INITE Directory server that lets an assistant find businesses which confirmed their own facts, by what they do and where, and look up one business's…

Streamable HTTPWeb executable

Location & Lifestyle3 toolsNov 1, 2026