Point your AI assistant at your links.
itty.foo runs an MCP server, so Claude and any other MCP-compatible assistant can create, edit, organize, schedule, and report on your branded links - in plain language, scoped to your account with an API key.
Works with Claude and any other MCP client.
What’s MCP?
MCP (Model Context Protocol) is an open standard that lets AI assistants connect to real tools and data, not just chat. itty.foo runs an MCP server that any MCP-compatible assistant can connect to using an API key you generate from your account.
Once connected, your assistant works entirely within your own account - it can only see and manage the links, folders, domains, and reports that belong to your organization. Nothing from other itty.foo accounts is ever visible.
You don’t need to learn a new interface. Just tell your assistant what you want - “shorten this URL and put it in my Marketing folder”, or “what were my top referrers last week?” - and it handles the rest.
What your AI assistant can do.
Manage your links, folders, and reports by talking to your assistant - the same everyday work you’d do in the dashboard.
Links
- Create, edit, and delete short links
- Set destination URL, description, and tags
- Move links between folders
- Schedule a link with start and end dates
Folders
- Create, rename, and delete folders
- List folders to keep links organized
- Group links by campaign, client, or project
Domains
- List and review your connected domains
- Add, update, or remove a domain (requires an org-admin sign-in)
- Set a per-domain default redirect (requires an org-admin sign-in)
Reporting
- Hourly and daily click reports per link
- Top countries, referrers, and user agents
- Full traffic breakdowns without opening a dashboard
Account
- Check which organization the API key belongs to
- Update organization details (requires an org-admin sign-in)
Audit logs
- Review raw request logs for your account
- Requires an org-admin sign-in, paginated for large accounts
The MCP tool reference.
itty.foo exposes 21 MCP tools over a single JSON-RPC endpoint. Read tools are read-only, deletes are explicit, and domain/organization mutations and log access require an org-admin sign-in - standard API keys act as regular-user principals.
View the full tool list
Links — link_list, link_get, link_create, link_update, link_delete
Folders — folder_list, folder_get, folder_create, folder_update, folder_delete
Domains (org-admin for create/edit/delete) — domain_list, domain_get, domain_create, domain_update, domain_delete
Organization (org-admin for update) — organization_list, organization_update
Reporting — report_link_hourly, report_link_daily, report_link_breakdown
Request logs (admin-only) — log_list
Endpoint: POST /api/mcp at https://app.itty.foo/api/mcp, JSON-RPC 2.0, stateless streamable-HTTP. Authenticate with an X-Api-Key header or a Klass Accounts OAuth bearer token - every call is scoped to the organization that owns the credential. API keys act as regular-user principals; admin-only tools (domain and organization mutations, request logs) require the OAuth token.
Connect in under a minute.
Any MCP client works - Claude, or another assistant that supports the standard.
claude mcp add --transport http itty-foo https://app.itty.foo/api/mcp --header "X-Api-Key: ifk_{secret}"
You stay in control.
Per-org, revocable keys
API keys are scoped to a single organization and can be revoked anytime from your account. Your assistant can never see another tenant’s data.
Read vs. destructive
Lookup and list tools are read-only. Deletes are explicit, separate tools - your assistant can’t remove a link or folder by accident.
Admin-only actions
Domain and organization changes, and raw request log access, require an org-admin sign-in through Klass Accounts - standard API keys can’t perform them.
Give your AI assistant the keys.
Get started with itty.foo for $99/year, then connect your assistant in under a minute.
Get Started