Skip to content
Connect your AI

Bring us into your AI.

Connect Claude Code, Claude, or any assistant that speaks the Model Context Protocol. Ask it what we do, have it read any page here, and scope your project from your own desk — your AI holds the conversation with our scoping tool, and we receive the same scope the contact page produces. No account, no key. Building something on it? The developer docs cover every door in detail.

The address

https://creweng.com/mcp

Two minutes

Set it up

Claude Code

In a terminal:

claude mcp add --transport http creweng https://creweng.com/mcp

Add --scope user to have it in every project, not just this one.

Already a client?

Create an access key under “Your AI” in your account, and add it as a header. Your AI can then read your projects, what we still need from you, your quotations and your invoices. Accepting a quotation stays with you, in your account.

claude mcp add --transport http creweng https://creweng.com/mcp --header "Authorization: Bearer <your access key>"

Claude (desktop or web)

Settings → Connectors → Add custom connector, and paste the address above.

Other MCP clients

Add it as a remote (Streamable HTTP) server. Most clients take a block like this:

{
  "mcpServers": {
    "creweng": { "url": "https://creweng.com/mcp" }
  }
}

The tools

What your AI can do

Ask about us

list_offersEvery product and service, who it is for, and where to read more.
list_pagesThe pages on this site your AI can read.
read_pageAny page, as Markdown — services, products, case studies, pricing.
search_knowledgeThe passages that answer a question, with the page each came from — the Guide's own retrieval.

Scope a project

start_scopingOpens a scoping conversation with our assistant. One sentence, or a question, is enough.
continue_scopingYour answers, and your questions — it explains, then asks what it still needs.
build_scopeTurns the conversation into a scope for you to read and correct.
submit_scopeSends it to us for a quote — only with your name, email and agreement.

Your projects (signed in)

my_projectsThe projects we have open for you, with their status.
my_projectOne project: the scope, what we still need from you, your quotations and invoices.
mark_item_sentRecords that you have emailed a checklist item to us.

Try asking

  • “Search Creweng's knowledge for how the Guide handles personal information.”
  • “What does Creweng still need from me for my project?”
  • “What does Creweng do for water and heat siting at a data centre, and which service fits a team at our stage?”
  • “We run a plant and want an AI agent assessed for what it may touch on our OT systems, under UK GDPR — scope it with Creweng.”
  • “Read this repo's README and our docs folder, draft a brief, and scope it with Creweng. Show me the scope before sending anything.”

What reaches us, and when

  • Reading pages and listing what we offer sends us nothing about you.
  • A scoping conversation is processed by Google’s Gemini model to answer and ask what’s missing. If you never send it, it is deleted within an hour of the last message.
  • Nothing reaches us until your AI calls submit_scope — and it is told to do that only after you have seen the scope and agreed to this, word for word: “I agree to Creweng, LLC using these details and this conversation to prepare a scope and reply to this enquiry, as set out in the privacy notice.”
  • Don't let your AI send passwords, keys or other people's personal information. It is asked not to, but it is your assistant.
  • Fair-use limits apply, per connection and across the site. If you hit one, the contact page reaches the same inbox.

Details in the privacy notice.