Settings
Developer settings
API keys, OAuth apps, and connecting the CLI or an AI client
Where: Settings, Developers
Availability: Feature availability and limits depend on this Nitty Music Social deployment. have it on every install.
This tab is the entry point to everything programmatic. The reference documentation lives in its own tabs; this page is about the controls in the UI.
Access
Your API key
Rotating is the fix if a key leaks, and the only fix: keys do not expire on their own.
MCP client configuration
Nitty Music Social generates the configuration block for connecting an AI client through MCP. Pick your client and copy the generated configuration block.
Apps
This is where you register an OAuth application, for building something other Nitty Music Social users will authorise, rather than something that acts as you.
Create OAuth App
Name and redirect URL are required. Description and icon are optional, and both are shown to users on the consent screen, so they are worth filling in.
Copy the credentials
You get a client ID and a client secret.
Implement the flow
API key or OAuth app?
| API key | OAuth app | |
|---|---|---|
| Acts as | You | Whoever authorises it |
| Good for | Your own scripts, automations, self-hosted tools | A product other Nitty Music Social users will use |
| Setup | Copy the key | Register an app, implement the flow |
| Revoking | Rotate the key | The user revokes in Approved Apps |
If you are automating your own posting, use the API key. Build an OAuth app only when other people’s accounts are involved.