Every connector is a new set of hands
An MCP server is a capability handed to an agent: a database it can query, an inbox it can send from, infrastructure it can change. These guides cover what each server exposes, the part worth governing, and the tags and rules to put in front of it.
None of them require a per-vendor integration. Prismor fronts any MCP server the same way: aggregate it behind one connector, evaluate every call against policy, scan every result as untrusted content.
Developer
Data
PostgreSQL
schema inspection and SQL queries against a live database
MongoDB
collection queries, aggregation, and document writes
Snowflake
warehouse queries across your analytics estate
Databricks
workspace queries, notebooks, and job runs
dbt
model metadata, lineage, and transformation runs
Supabase
database, auth, and storage for a live project
Communication
Business
Salesforce
accounts, contacts, opportunities, and custom objects
HubSpot
contacts, deals, tickets, and marketing email
ServiceNow
incidents, change requests, and CMDB records
Jira
issues, sprints, comments, and transitions
Linear
issues, projects, cycles, and comments
Stripe
customers, charges, subscriptions, and refunds
Infrastructure
Knowledge
Your server not listed?
It does not need to be. The gateway fronts any MCP server, including ones you wrote yourself, and tags tools by behavior rather than by a list of known names.
Product names are trademarks of their respective owners. Prismor is not affiliated with or endorsed by any of them, and the MCP servers described here are third-party software.