01
Choose a service
Use a supported custom MCP connection when the work needs a tool beyond the built-in connector catalog. Start with the connection options available in your account.
Product / Connectors / Mcp
Bring additional tools into the same working context.
Supported custom MCP connections extend the tools available to Praxa while keeping actions subject to the same permission policies.
Read the integration docsChoose the tool connection
Use a supported custom MCP connection when the work needs a tool beyond the built-in connector catalog. Start with the connection options available in your account.
A CLOSER LOOK
Bring additional tools into the same working context.
Supported custom MCP connections extend the tools available to Praxa while keeping actions subject to the same permission policies.
Your working context
The tools you choose.
GmMail
Gmail
Ca
Google Calendar
Schedule
Dr
Google Drive
Files
Sl
Slack
Conversations
N
Notion
Knowledge
GH
GitHub
Code
An example of connected apps in your working context.
01Choose the tool connection
+
Use a supported custom MCP connection when the work needs a tool beyond the built-in connector catalog. Start with the connection options available in your account.
02Keep authority explicit
+
An additional tool remains governed by its connection and action boundaries. Consequential operations still require approval; a new connection is not permission for every action it exposes.
03Build from the documented contract
+
Developer documentation covers the integration surfaces and their credential boundaries. Use the current guidance for authentication, approvals, and observing the result of a request.
SUPPORTED APPS
Start where your work already lives.
Mail, calendars, files, conversations, knowledge, and code. Choose from the connections available to your account.
Explore the catalogCUSTOM CONNECTIONS
Bring another tool to the task.
Supported custom MCP connections extend the available tools within the same action policies and permission boundaries.
Explore MCP connectionsHOW IT WORKS
Work across the tools you already chose.
02
Grant the right access
An additional tool remains governed by its connection and action boundaries. Consequential operations still require approval; a new connection is not permission for every action it exposes.
03
Review meaningful changes
Developer documentation covers the integration surfaces and their credential boundaries. Use the current guidance for authentication, approvals, and observing the result of a request.
Your mission,
our focus.
Start with a request and see how Praxa can carry your work forward.
Get started