Spotka speaks MCP.
Add one line to Claude, Cursor, or any app that speaks MCP, and it can find things to do, make events, and answer invitations for you — in your name, with your own account.
https://spotka.co/api/v1/mcpIt speaks MCP over plain HTTP — one POST per message, which is what Claude,
Cursor and Windsurf send. Your key travels in an X-API-Key header.
There is nothing to install and no server to run. Two protocol
versions are supported, 2025-06-18 and 2025-03-26; your
app picks one on its own.
Open Spotka on the web, Android or iPhone and go to Settings → API access → Create a key — or jump straight there:
You get a short key like spk_4KAS22M1JQFQ. It is shown once. If you
lose it, make a new one — it takes one tap, and you can revoke the old one on the
same screen.
A key belongs to one person: yours. Whatever you connect can do only what you can do in the app yourself.
claude mcp add --transport http spotka https://spotka.co/api/v1/mcp \
--header "X-API-Key: spk_XXXXXXXXXXXX"These keep a small config file listing the MCP servers they use. Add Spotka to it:
{
"mcpServers": {
"spotka": {
"type": "http",
"url": "https://spotka.co/api/v1/mcp",
"headers": { "X-API-Key": "spk_XXXXXXXXXXXX" }
}
}
}Then restart the app. Spotka's tools show up in its tool list.
Some apps have nowhere to put a header. Put the key in the URL instead — it works exactly the same:
https://spotka.co/api/v1/mcp?key=spk_XXXXXXXXXXXXTreat that URL like a password, because it now contains one.
| Tool | What it does |
|---|---|
ideas | Things to do in the city, picked for you |
events | Events other members are hosting that suit you |
my_events | Events you host, events you joined, invitations waiting for you |
create_event | Add an event |
update_event | Change an event you host — partial, so anything you leave out stays as it is |
invite | Invite people to an event — or make the event and invite in one go |
event | One event in full: status, guests, who is interested |
join | Take a seat at someone else's event |
leave | Give up a seat you took |
respond | Accept or decline an invitation — or, as the host, approve a guest's proposed time |
archive | Retire an event you host |
delete_event | Delete an unpublished draft |
inbox | What is waiting: unread conversations and invitations |
conversation | One conversation, without marking it read |
mark_read | Mark a conversation read, on purpose |
send_message | Send a message as you — needs a key with messaging enabled |
activity_history | What this API changed on your account |
revoke_invite | Take back an invitation you sent |
calendar | What you have coming up, hosted and joined |
profile | Your own profile — public half and private context |
update_profile | Change your own profile; only the fields you name |
capabilities | What your key may do, what each tool changes in the world, and how much budget is left |
next Friday at 7pm, not a date format. Spotka works it out, and tells
it plainly when a time was not understood — so it can never report an event as
Sunday when no time was saved.
A few more tools — actors, seed and
reset — exist for writing test suites and work only with a test key.
They are described in the
full API guide.
Once it is connected, just ask in ordinary words:
If you would rather not use MCP at all, the same things work with
one curl line — see the
full API guide.
They go out in your name, so it is worth telling your assistant to check with you before it invites anyone.
Same key, same limits as the rest of the API — a per-minute and per-day call
budget, a tighter one for events and invites, and a daily cap on people invited.
What you have left is in the X-RateLimit-Remaining header of every
reply.
The numbers, and how long each call takes, are on the full API guide — kept in one place on purpose, so the two pages cannot quietly disagree about them. If you need more, write to support@spotka.co.