mcp-tool

For SaaS and API teams

Let customers use
your product
inside ChatGPT.

Turn a customer question into a product search, availability check or qualified request — using your actual product data.

$4,900 fixed · 10 business days · You own the code

30 minutes with Gorden · Scope agreed before work starts

FROM QUESTION TO REQUESTIllustrative example
CUSTOMER ASKS“Find a pump for 8 bar that ships to Germany this week.”

ChatGPT → your connected product

Your catalogue.
Your availability.

Search requirementsCheck stockPrepare request
RESULT TO VERIFYA quote request with product + requirements

Example workflow, not a live API call. Tools and actions depend on your API and the agreed scope. The user connects your product first.

One useful customer task

From a question
to something your product can do.

Choose the task your customers already need. Give them a way to complete it from a connected conversation.

01 /

Find the right product

Let customers search your catalogue with their requirements, using your actual product data.

02 /

Carry context into the request

Use the selected product and customer requirements to prepare a quote request, rather than asking them to start again.

03 /

Define a result you can verify

Agree what success means before building: a matching item, an availability check or a prepared request. Test it against your own data.

Our own working implementation

A real MCP.
Open for inspection.

We built WebMCP Tool, our website readiness scanner. Its public MCP exposes website scoring and explanations as tools you can connect to an assistant.

This is our own product. Inspect the implementation, then discuss how the same connection pattern could serve your customers.

Inspect WebMCP Tool ↗

A workflow you can examine

Ask about a website.
Get a readiness assessment.

  1. A user provides a public website URL.
  2. The connected assistant calls the scoring tool.
  3. The scanner returns findings the assistant can explain.

Technical proof from our own product. It is not evidence of customer revenue or conversion uplift.

MCP Tool / Launch · Available now

One agreed workflow.
A connection you can test.

Fixed-price Build

$4,900USD / one-time · 10 business days

Search, check availability or prepare a request. We choose the customer task together and build the tools it needs.

  • Up to eight tools from your API or website
  • Authentication, staging and deployment
  • First 30 days of hosting and monitoring
  • Submission preparation and reviewer feedback fixes
  • Your repository, code and deployment instructions

50% deposit; balance on delivery. The timeline starts when agreed inputs are ready. Platforms decide directory acceptance.

How we deliver

Agree it. Try it.
Own it.

  1. Agree the result. Bring your API docs. We write down the task, tools and access before work starts.
  2. Test your workflow. Try real questions against your test data on a staging endpoint.
  3. Take ownership. Get your code and deployment instructions, with submission preparation.

Already have a server, or need ongoing maintenance? See Listing Sprint and optional Care →

Already have an MCP? · Commerce early access

Give your tools
an offer buyers understand.

Have valuable data or actions and customers who want access? Help shape paid plans, usage limits and seller reporting around your existing endpoint.

Discuss your paid MCP ↗

Commerce is in planning. Checkout and the gateway are not live. Pilot scope and pricing agreed before integration.

Your direct contact

Talk to the person building it.

Gorden Wübbe runs your project from the first conversation to testing and handover. He built WebMCP Tool and Agent Tracking.

Talk to Gorden ↗

Before you commit

A few straight answers.

What does the $4,900 Build include?

Up to eight tools over your API or a read layer over your website, authentication, staging, deployment, 30 days of hosting and monitoring, submission preparation and code in a repository you own. We agree the scope before work starts. Additional interfaces, integrations and Commerce work are scoped separately.

When do the ten business days start?

Once kickoff is complete and the agreed API documentation, authorised access and test data are available. The timeline covers our build and submission preparation; platform review timing is separate.

Will this automatically bring us customers?

No. A connector lets an assistant use your product after a user or organisation connects it. You still need a plan for discovery and adoption. We build and test the customer workflow; we do not guarantee leads, revenue or directory acceptance.

Can we sell access to an existing MCP?

Commerce is in early access planning for teams with an existing endpoint. We are working with founding sellers on paid plans, controlled access and usage reporting. The offer builder is a preview; self-service payments, access provisioning and metering are not live yet. Pilot scope and pricing are agreed before integration.

Can we talk before paying?

Yes. Bring your product URL or API docs to a 30-minute call with Gorden. We agree the customer task and check whether the fixed scope fits. Build is paid 50% upfront, with the balance on delivery. You can host the delivered code yourself; ongoing Care is optional.

Start with your customer

What should they be able
to do with your product
from ChatGPT?

Bring your product URL or API docs. We’ll discuss one useful workflow and whether the fixed-price Build fits.

30-minute call · No purchase required