ShooFly for developers

People keep one profile in ShooFly: interests, how they like answers, their work, accessibility needs. With their permission, your app can read it to personalize from the first screen, instead of asking again.

AI apps: connect over MCP

Add this server as a remote MCP connector. It signs people in with OAuth and offers get_profile, list_modes and suggest_update.

https://mcp.getshoofly.app/mcp

Any app: sign in with ShooFly

Standard OAuth 2.1 with PKCE. Register your app once (dynamic client registration), send people to authorize, exchange the code for a token.

Discovery   https://auth.getshoofly.app/.well-known/oauth-authorization-server/auth/v1
Register    POST https://auth.getshoofly.app/auth/v1/oauth/clients/register
Authorize   https://auth.getshoofly.app/auth/v1/oauth/authorize
Token       POST https://auth.getshoofly.app/auth/v1/oauth/token

People see a consent screen and choose which profiles (Personal, Work, Creative) and which details you get. They can change or revoke that any time in the ShooFly app.

Read the profile

curl https://mcp.getshoofly.app/v1/profile \
  -H "Authorization: Bearer $ACCESS_TOKEN"

{
  "mode": "personal",
  "version": 7,
  "profile": {
    "interests": [{ "label": "Trail running", "visibility": "shared" }],
    "ai_preferences": { "language": "en", "tone": "Direct", "answer_length": "Short", "expertise": [] }
  }
}

GET /v1/modes lists the modes shared with you; pass ?mode=work to /v1/profile for another one.
POST /v1/suggestions with { "change": { "type": "add_interest", "label": "Climbing" }, "reason": "…" } sends a suggestion to the person's inbox. You never write the profile directly.
You only ever get the fields they shared. Hidden items and sensitive topics are left out unless they chose to share them.
Every read is shown to the person, with your app's name.