Platform/Connectors

40+ servers on day one. Anything else, you bring.

Add a server URL. Nexus discovers its tools, generates config forms, and surfaces them on the palette. The vendor maintains the integration. You don't.

Bundled

Production-ready MCP servers.

Hosted, monitored, and updated by the Nexus team. Drop them on any canvas — credentials configured per workspace, scoped per workflow.

GitHub
repos · issues · PRs
Salesforce
SOQL · objects · flow
Slack
post · search · DMs
AWS
EC2 · S3 · IAM · SES
Stripe
payments · subscriptions
Postgres
SQL · schemas · txns
HubSpot
CRM · marketing
Notion
pages · databases
Snowflake
warehouses · queries
Linear
issues · cycles · projects
Anthropic
Claude · prompt cache
OpenAI
GPT · embeddings
Confluence
spaces · search
SharePoint
sites · files · lists
Google Drive
docs · sheets · search
Jira
issues · workflows
PagerDuty
incidents · schedules
Datadog
metrics · logs · APM
Twilio
SMS · voice · WhatsApp
SendGrid
email · templates
Zendesk
tickets · macros
Intercom
conversations · users
Okta
users · groups · SCIM
DocuSign
envelopes · signatures
Bring your own

Any MCP server. No code changes our side.

Paste the server URL, configure auth once, and Nexus calls tools/list. Tools appear on the palette with their input/output schemas — auto-generated config forms, ready to drop into any workflow.

Add a server

Three fields. That's it.

name:    internal-billing-mcp
url:     https://billing.internal/mcp
auth:    oauth | api-key | mTLS

Discovery refreshes on a cron. New tools appear automatically.

Schemas, not screenshots

Auto-generated config forms.

Every tool's input schema becomes a form. Required fields, enums, nested objects — rendered correctly without us writing a UI per tool.

Output → upstream

Typed wires.

Output schemas mean downstream nodes know exactly what fields are available. No string-matching guesses.

Per-workspace creds

Scoped, audited, rotatable.

Credentials live in AWS Secrets Manager. Per environment. Per workspace. Per workflow if you want.

Wire up your stack

One protocol. Every service. Day one.

Bring your MCP servers — or use ours. We'll walk you through hooking up an in-house server live, end to end.