Find a service. Prepare a brief.

Start with the website

Use the service finder to describe the work and select a platform. Results link to service details and relevant published work or examples. You can then add a service to the project brief.

Supported browsers may make these same actions available to an assistant through WebMCP. The regular service finder and brief form remain available when that browser capability is absent.

The two tools

• lookup_services accepts an optional task description and platform. It returns matching public services with their descriptions, links and supporting examples. Matching uses the service catalog and its topic tags.
• prepare_project_brief requires project goals and accepts supplied engagement, platform, website, budget and timeline answers. It returns normalized draft answers and identifies unanswered required project fields. It does not guess preferences.

On the Contact page, browser preparation can fill empty project fields. It stops if it would replace a different existing answer or if review or sending is already open. An assistant cannot use this tool to enter your name, email or consent, open the review, or send a message.

Review before sending

1. Check the draft project answers and complete any missing answers.
2. Enter your name, organization and email in the contact form.
3. Select Review project brief and read the summary. Use Edit if anything needs changing.
4. Choose whether to give the required delivery consent and send. Existing spam and delivery checks still apply.

Preparing a draft does not save an inquiry or contact dirango. The remote preparation tool returns draft data; it cannot transfer that data into a different browser session. Do not include passwords, credentials or confidential client records in project goals.

Connect an agent client

Our public, stateless MCP endpoint is https://dirango.com/mcp. It supports Streamable HTTP requests and the published MCP 2025-11-25 protocol. Only service lookup and brief preparation are exposed. There is no account or authorization token to obtain for these public operations.

HTTP clients can use GET /api/agent-services for the catalog, POST /api/agent-services for lookup and POST /api/agent-brief for preparation. POST bodies must be JSON, use documented fields and fit within 16 KiB. Preparation responses require human review and point to the Contact page.

curl https://dirango.com/api/agent-services \
  -H 'Content-Type: application/json' \
  --data '{"query":"ongoing support","platform":"wordpress"}'

Read the OpenAPI contract, API catalog, public service catalog or project brief skill instructions. The MCP server card and skill index are discovery hints; their formats are experimental and client support varies.

Public information and privacy

The catalog is built from published service pages and approved public examples. It excludes queued articles, private monitoring and contact delivery operations. Lookup never visits a supplied website URL. Remote preparation processes the supplied project answers to return a draft, without saving an inquiry or sending email. Ordinary hosting security logs may still record requests. Read our privacy information.

For implementation evidence and limitations, read our agent-ready website case study.