MCP (everything else)
Use Airskills with any MCP-compatible agent
MCP integration
Airskills exposes an MCP (Model Context Protocol) server that lets any MCP-compatible agent list and load the skills your account can read. The MCP endpoint is read-only; use the CLI to push changes.
The MCP endpoint is:
https://airskills.ai/mcp
Connecting a client
Add https://airskills.ai/mcp as an MCP server in your client. When you first connect, the client opens a browser window and asks you to sign in to airskills. After you approve, the client receives an access token automatically and can use the server. There is no API key to copy or paste.
Specifically, the server implements MCP Authorization — OAuth 2.1 with PKCE and Dynamic Client Registration. Any spec-compliant MCP client (Claude Desktop, Cursor, ChatGPT desktop, Goose, Cline, etc.) handles the flow without configuration.
Example: Claude Desktop
-
Open Settings → Developer → Edit Config.
-
Under
mcpServers, add:{ "mcpServers": { "airskills": { "url": "https://airskills.ai/mcp" } } } -
Restart Claude Desktop. The first time you use an airskills tool, a browser window opens for sign-in.
Other clients
Anything that supports MCP authorization works the same way — point it at https://airskills.ai/mcp and complete the sign-in when prompted.
Managing connected apps
Sign in to airskills.ai/dashboard/connections to see which apps you have connected and revoke any of them. Revoking immediately signs that app out of your account.
Scopes
When you authorize a client you grant it specific scopes:
skills:read— list and read your skills and skillsetsaccount:read— read your account profile
You are shown the requested scopes on the consent screen before approving.
Endpoints
Spec-compliant clients discover these automatically. The well-known URLs are:
/.well-known/oauth-authorization-server— RFC 8414 metadata/.well-known/oauth-protected-resource— RFC 9728 metadata
Was this page helpful?