Quilr-Provided MCPs

Quilr-provided MCPs are integrations built and operated by Quilr for products that need a broader, safer, or more agent-friendly tool surface than a provider's standard connector. Install them from the MCP Library, then use the MCP Gateway to control tools, guardrails, access, and audit logs.

FLAGSHIPMicrosoft 365 v39 workloads. 1 governed MCP.ENGINEERINGAzure DevOps AdvancedDelivery intelligence + controlled actionsSAFETY-FIRSTAthenahealthFHIR + athenaOne with PHI-safe controlsINTELLIGENCESemrush Advanced23 explicit SEO and market tools

This is different from a custom MCP server that your organization registers by URL. See MCP Library for that workflow.

If the provider also publishes an MCP server, use the Official MCP Comparison to understand which option is broader and what Quilr adds.

Choose An Integration

Integration	Best for	Main capabilities	Connection	Changes data?
Microsoft 365 v3	Mail, calendar, OneDrive, OneNote, Teams	Search, read, send, schedule, files, notes, collaboration	Microsoft OAuth	Yes
SharePoint	Sites, document libraries, lists	Find, list, read, upload, update, delete	Microsoft OAuth	Yes
Excel	Cloud workbooks	Ranges, formulas, formatting, tables, charts, pivots	Microsoft OAuth	Yes
Microsoft Tasks & Planner	Personal and team work planning	To Do lists/tasks and Planner plans/buckets/tasks	Microsoft OAuth	Yes
Azure DevOps Advanced	Engineering delivery	Repos, pull requests, boards, pipelines, tests, wiki, security	Microsoft OAuth	Yes
Jira	Issue and project workflows	Issue, project, search, comment, and workflow operations	Atlassian OAuth	Yes
Confluence	Knowledge bases	Spaces, pages, search, comments	Atlassian OAuth	Yes
Google Workspace	Gmail, Calendar, and Drive	Search/read mail, drafts/send, events, Drive discovery/export	Google OAuth	Yes
Figma	Design-to-code and review	Design context, screenshots, variables, comments, Code Connect	Figma OAuth	Yes
Calendly	Scheduling operations	Event types, invitees, routing, webhooks, availability	Calendly OAuth	Yes
HubSpot CRM	CRM records	Search, batch read, associations, create, update, archive	HubSpot OAuth	Yes
Avoma	Meeting intelligence	Meetings, transcripts, notes	API key	No
Writer	Enterprise generative AI	Chat, apps, knowledge graphs, files, translation, vision, web search	API key	Limited
Optimizely Experimentation	Experiment analysis and operations	Results, schemas, reporting, lifecycle, collaborators, datafiles	Customer OAuth app	Yes
Semrush Advanced	SEO and market research	Domains, keywords, backlinks, traffic, projects, batch analysis	API key	No
BrowserStack Advanced	Test operations and diagnostics	Browser/device inventory, Automate, App Automate, test management	Username + access key	Yes
Athenahealth	Clinical system integration	athenaOne and FHIR reads, controlled writes, bulk export jobs	Customer OAuth app	Yes, gated
Tavily	Agent web research	Search, extract, map, crawl, research, usage	API key	No
Cycode	Code security	Service status and secret scanning	Optional provider auth	No
Quilr Web Search	Lightweight search and page retrieval	Web search and webpage extraction	Managed	No

note

“Changes data?” describes the integration's available tool surface, not what every user can do. Administrators can disable write or destructive tools in Tools Management and restrict agent access through Access Control.

Quilr-Provided vs Provider-Native vs Your Own

Option	Choose it when	Operations	Credentials and updates
Quilr-provided MCP	You want a curated tool surface with gateway-aware safety and enterprise workflows.	Quilr operates the MCP; your admin controls exposure through the gateway.	Quilr maintains the server. Users or admins still supply provider authorization where required.
Provider-native MCP	The provider's official MCP already covers the workflows you need.	The provider operates the upstream server; Quilr secures and governs access.	Follow the provider's connection model. See Provider Setup.
Organization custom MCP	You have an internal system or your own MCP implementation.	Your organization operates the server; Quilr proxies and governs it.	Register its reachable /mcp or /sse URL in the library.

Common Safety Model

• Read, write, and destructive tools are labeled so administrators can apply least privilege.
• OAuth and API credentials are scoped per connection and are not passed to the AI model.
• Destructive operations use explicit confirmation where the integration supports them.
• MCP Gateway policies can scan tool inputs and outputs and retain auditable tool-call metadata.
• Availability and exact tools can vary by tenant, provider plan, granted scopes, and administrator policy.

Open any integration above for its focused capability matrix, Quilr differentiation, safety model, and setup links.