Where it fits
Legal teams and in-house counsel with a Definely licence who review agreements and want clause-level analysis in Claude.
- Review clauses in a supplied agreement.
- Reason over the language of a specific contract.
- Analyze agreement language during contract review.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Definely
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Explore what the user wants, what they assume, and which approach is worth committing to before any creative work. Use before building a feature, component, plan, or other new work where a wrong direction is costly.
Ask which skill or flow fits a situation. It routes among the user-invoked skills in this repository.
Interview the user about a plan or design until its assumptions and trade-offs are clear.
No skills found
Try a different search term or clear the filters.
Claude connector setup (region-specific)
Requirements: an active Definely licence, a Definely account, and Claude access. The UK connector-store listing is configured for the UK region by default. US customers add a custom connector with the URL shown. Other regions should contact Definely for the correct endpoint.
- Confirm your Definely region
The Claude connector-store listing is UK by default. US customers use https://mcp.us.definely.com; other regions must contact Definely support for the correct host.
- UK: add from the connector catalogue
In Claude admin settings, browse connectors, find Definely in the catalogue, and add it to your organisation. Each user then connects and signs in with their Definely credentials.
- US: add a custom connector
In the Claude admin console, open Connectors, choose Add custom connector, name it Definely US, and enter https://mcp.us.definely.com. Deploy it to the relevant users, who sign in with their Definely email.
- Allow the document-upload host
Document uploads go to your own tenant bucket. A Claude Owner or Admin must allow the tenant's upload hostname under claude.ai/settings/capabilities network egress; ask Definely for that hostname.
Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name definely. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
definelyappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Review clauses in a supplied agreement. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. The provider page was available when we checked.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
- The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Definely documentationhttps://help.definely.com/en/articles/634922-definely-s-connector-for-claude