MCP toolsAccount and sitesUpdated
Sign up
What does mttr_signup do?
Signs you up with your email and answers your key. It is the one call that works before there is a key, so your assistant can do it without you leaving the chat. Anyone may make this call, before there is a key.
When to use it
- Your assistant is connected to mttr but has no key yet.
- You want to start from the assistant rather than the website.
What you ask
You say“Sign me up for mttr with [email protected].”
Your assistant calls
mttr_signup({ email: "[email protected]" })
| Argument | Type | Needed | What it is |
|---|---|---|---|
email | Text | Yes | The person's email address. |
What comes back
- Your key, shown once. Keep it where your assistant can read it.
- The command that connects your assistant again with the key.
- What the key reaches: any public site’s report at once, and your own site’s private parts once you claim it.
- Email given
- 2Key made
- 3Connected with the key
- 4Site claimed
Your key starts mk_ and is shown once. Connect again with it, then claim your site.
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
Signing up is the one call made before there is a key, so it goes to /mcp whatever asks for it:
curl https://mttr.si/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "mttr_signup",
"arguments": {
"email": "[email protected]"
}
}
}'The call in full, with its HTTP address, each argument’s type, who may make it and the call in four languages, is mttr_signup in the API reference.