MCP Connectors
MCP (Model Context Protocol) connectors let you connect Workjet to external tools and services. When an AI model has access to connectors, it can read files, query databases, search the web, create tickets, post to Slack, and more — all from within the chat or as part of an assistant or engine workflow.
What is MCP?
The Model Context Protocol is an open standard for connecting AI models to external data sources and tools. Each MCP connector runs as a local server process that the Workjet desktop app communicates with over standard I/O. The model sends tool-call requests to the connector, and the connector executes the action and returns the result.
This architecture keeps credentials local to your machine and gives you granular control over which tools each assistant, engine, or chat session can access.
How Connectors Work
- The AI model decides it needs to use a tool (e.g., query a database)
- Workjet sends the tool-call request to the appropriate MCP connector process
- The connector executes the action using the configured credentials
- The result is returned to the AI model for incorporation into its response
Local execution: MCP connectors run as local processes on your machine. API keys and tokens never leave your device — they're stored in the OS keychain and injected as environment variables at connector startup.
Connection Wizard
Every connector in Workjet uses a three-step connection wizard:
Step 1: Configure
The wizard displays the pre-filled command that starts the MCP server and provides input fields for required environment variables (API keys, tokens, connection strings). Each connector has different requirements — some need no configuration at all (like Filesystem and Memory), while others require API keys or OAuth tokens.
Step 2: Test
Click Test Connection to validate your credentials and verify that the MCP server can be started successfully. The wizard checks:
- The MCP server binary is available
- Environment variables are set correctly
- The server starts and responds to a health check
- Credentials are valid (for connectors that require authentication)
Step 3: Save
Once the test passes, click Save to store the connection. The connector appears in your sidebar with a green status indicator showing it's active.
The Hangar (Marketplace)
The Hangar is the MCP connector marketplace within Workjet. It provides a curated catalog of connectors with one-click installation. Browse the Hangar to discover connectors for services your team uses.
Each connector in the Hangar includes:
- Description of what the connector does
- Required environment variables and how to obtain them
- List of available tools (actions the AI can perform)
- Setup instructions
Available Connectors
Workjet ships with 14 first-class connectors covering development, communication, productivity, databases, search, and more. See the complete connector reference for the full list with configuration details.
Connector Permissions
Each connector is assigned to specific assistants, engines, or chat sessions. This follows the principle of least privilege:
- A customer support assistant gets Slack and Linear, but not PostgreSQL
- A data analysis engine gets PostgreSQL, but not GitHub
- An interactive chat session can be granted any combination of tools
Security note: Only grant connectors to assistants and engines that actually need them. Tools like Filesystem and PostgreSQL have broad access to your local system and databases.
Next Steps
- View the full connector reference
- Set up assistants with tool access
- Create engines that use connectors for data gathering