MCP, the Model Context Protocol, is how AI assistants connect to other software. Connect yours to Wizard Application and it can look up and update your leads, candidates, jobs, companies, bookings and content, or hand a job to one of your AI employees.
Before you start
- MCP uses the API, so it is on the Professional and Enterprise plans.
- Each request your assistant makes counts towards your monthly API requests.
- Only an admin can connect an assistant.
Connect your assistant
-
Copy your MCP address
Open Settings from the gear icon in the top bar and choose API Keys. Under Connected assistants, copy the MCP server URL. It is your workspace address followed by /api/v1/mcp, for example https://your-workspace.wizardapp.io/api/v1/mcp.
-
Add it to your assistant
In your assistant's settings, add a custom connector or MCP server and paste the address. Leave any key or token fields empty.
-
Sign in and choose what it can do
Your assistant sends you to Wizard Application. Sign in, check the address it will send you back to, and tick only what it needs. Read permissions let it look things up, write permissions let it create and update records. Tick AI employees: give jobs if it should be able to ask your AI employees to do work. Then choose Allow.
-
Try it
Ask your assistant something like List my newest leads. It only sees the tools you allowed.
What it can and cannot do
- It can list, open, create and update leads, candidates, jobs, companies and bookings, convert a lead, read your team list and work with your content, as far as you allowed.
- It cannot delete anything or add team members. Those stay in the app and the API.
- Asking an AI employee gives it a job in plain words. It works with the tools its role allows, and any change it wants to make waits in its action queue unless you trust it with that change.
Change or disconnect an assistant
Every connected assistant is listed under Connected assistants with who connected it and when it was last used. Choose Disconnect and it loses access straight away. To change what it can do, connect it again and tick a different set.
Use an API key instead
Agents you build, and tools that let you set request headers, can use an API key rather than signing in. Create a key under API Keys, tick its permissions, and send it as a bearer token in the Authorization header to the same address.
One connection per assistant. Connect each assistant on its own, so you can disconnect one without affecting the others.
For the technical details, see the API documentation. For keys in general, see Connect with the API.