Connect your assistant to Overskill to build, edit and publish apps from the chat you already use. The hosted MCP connection uses https://mcp.overskill.com/mcp and opens Overskill sign-in in your browser.
MCP is the connection between your assistant and Overskill's tools. Your assistant needs support for a remote Streamable HTTP server with OAuth sign-in. The available setup controls depend on your assistant and workspace.
Connecting your agent
- Open Connect Overskill for the current setup instructions for your assistant. Workspace plans may require an administrator to enable custom connectors first.
- Add a remote MCP server or custom connector with this URL:
https://mcp.overskill.com/mcp. - Choose OAuth if your assistant asks for an authentication method. Complete the browser sign-in, select the Overskill team you want to use, and review the requested permissions.
- Return to your assistant and check that it can see Overskill's tools. Start with a read:
list_appsfinds apps on the connected team;get_balancereads that team's balance and plan.
You do not need to paste an API key into this MCP connection. Keep passwords, tokens and API keys out of chat prompts.
The connection stays attached to the team you selected during consent. Switching teams in the Overskill website does not move that connection; connect again for another team.
No account yet? Create your Overskill account, then complete the connection. A successful sign-in or read does not establish builder access. Review your team's access, permissions and available credits before requesting a build. See current plans and pricing.
Build one workflow, then check it
With the required access, your assistant can use Overskill's available tools to create an app, inspect a build, request changes and publish. Ask it to list the tools available to your connection rather than assuming every account has the same tools.
Start with one person, one task and a result you can test. For example:
Help me plan a workshop app with fictional data. First check my connected Overskill team's apps and balance. Draft the app brief and the checks we will run before starting a build.
Then follow Build, test and publish an app through MCP for a worked brief, a build-and-repair sequence and an editable handoff worksheet. Keep the returned build identifier so later status checks and repairs target the same work.
Open the preview and test the actual result. A completed build status does not prove that records survive a reload, private access is correct, or a payment connection is ready. After publishing, open the public URL and repeat the relevant checks.
If the connection does not work
| What you see | What to check next |
|---|---|
| Your assistant cannot connect to the server | Use https://mcp.overskill.com/mcp in the remote-server field. The server-card JSON and SKILL.md links describe Overskill; they are not MCP connection URLs. Check your client's remote MCP and OAuth support on Connect Overskill. |
| Sign-in finishes, but the apps are from the wrong team | Check the team selected during consent. Connect again for the intended team; changing the website's current team does not change an existing connection. |
| A tool is unavailable or access is refused | Inspect the returned reason and the tools your connection exposes. Account permissions and available features still apply. Do not repeatedly retry the same refused action. |
| A build stops because credits or access are missing | Read the balance and the reported requirement. Resolve the access or credit issue, then check the existing build before starting another copy. |
If you need help, include your assistant's name, the step that failed and the error text. Omit credentials and private app data.
REST API and discovery documents
If you are writing your own API integration, use Getting started with the Overskill partner API for its authentication and request format. The REST API's API-key setup is separate from hosted MCP's OAuth sign-in.
These public documents help an assistant discover and understand Overskill:
- [MCP server card](/.well-known/mcp/server-card.json): connection metadata, including the transport endpoint and authentication details. Use the endpoint it describes, not the card's URL, as the MCP server address.
- SKILL.md: the build, deploy and management guide for skill-style agents.
- llms.txt: a short site map, with llms-full.txt providing additional reference material.
- AI Agents: an overview of using Overskill from an assistant.
- Every public help article also has a
.mdaddress, such as this article as Markdown.
For REST automation, check GET /api/v1/capabilities for the account's current permissions and follow the action-specific response instructions. Overskill API errors and how to handle them explains access refusals, credit blocks and retry behavior. API discovery does not grant permission to spend, publish or act on another account.
Pricing for agent-driven usage
Builds and AI edits draw from the connected team's credits. There is no separate agent tier. Check the team's balance and current pricing before starting work; connected services may have their own setup and charges.