MCP Server
Connect an AI assistant to Pixelwand CRM with OAuth to find records, update your CRM, and explore reports.
The Pixelwand CRM MCP server lets compatible AI assistants work with your CRM account. Find leads and deals, review activity, prepare follow-ups, manage tasks, and explore Reports using natural language.
Connection details
| Setting | Value |
|---|---|
| Server URL | https://crm.pixelwand.io/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth |
| CRM sign-in | Sign in to Pixelwand CRM |
Use the complete server URL, including /mcp. Let your assistant manage OAuth discovery and sign-in; do not put your CRM password or bearer token in its configuration file.
Connect your account
- In your assistant's MCP settings, add a remote server named Pixelwand CRM.
- Enter
https://crm.pixelwand.io/mcpand choose OAuth authentication. - Start the connection. When Pixelwand opens, sign in with the CRM account you want the assistant to use.
- Review the access request and approve it.
- Return to the assistant and ask, “Which Pixelwand teams can I access?”
Your assistant and CRM accounts do not need matching email addresses. The CRM account used during OAuth determines the connected identity. If you belong to several teams, specify which team to work in.
For ChatGPT, follow OpenAI's custom MCP connection instructions. Account and workspace policies determine whether custom MCP connections are available. This connection guide does not imply that the public Pixelwand plugin is already listed in the directory.
Examples
- “Find leads for Acme in my team.”
- “Open this deal and summarize its recent activity.”
- “Give me a briefing of recent leads and deals.”
- “Show my reports from October 1 to October 8.”
- “Show reports for Priyal and me last week.”
- “Prepare a follow-up email for this lead.”
- “Save this email as a draft.”
Review the target record, recipient, and content before requesting a message to be sent. Preparing text, saving a CRM draft, and sending a message are separate actions. The daily briefing shows recent records; it is not a complete audit of everything changed today.
Records and interactive reports
In hosts that support MCP Apps, lead and deal search results and detail tools can show interactive cards with Open in CRM links. Reports can show charts, exact-value tables, date presets, and member filters. Hosts without MCP Apps can still use the tools and their text results.
Reports use the same backend calculations, plan access, and member visibility as the CRM Reports page. Team owners and admins can filter by one or several members. Other team members see their own statistics. Selecting several members combines their results; it does not produce a side-by-side comparison. The Open full report link opens Reports in CRM but does not carry over the panel's filters.
Available tools
The server exposes 40 tools. Clients discover each tool's input and output schemas, readable title, description, and safety annotations through MCP.
| Purpose | Tools |
|---|---|
| Connected account and teams | crm_whoami, crm_list_teams |
| Leads | crm_search_leads, crm_get_lead, crm_create_lead, crm_update_lead, crm_assign_lead, crm_convert_lead_to_deal |
| Deals | crm_search_deals, crm_get_deal, crm_create_deal, crm_update_deal_stage, crm_mark_deal_won_lost, crm_stalled_deals |
| Organizations and contacts | crm_search_organizations, crm_organization_360, crm_create_contact |
| Reports and summaries | crm_get_reports, crm_pipeline_summary, crm_daily_briefing, crm_aggregate_metrics, crm_call_stats |
| Tasks and activity | crm_search_tasks, crm_create_task, crm_complete_task, crm_get_timeline, crm_add_timeline_note, crm_log_call |
| Campaigns and queues | crm_list_campaigns, crm_enroll_in_campaign, crm_pause_enrollment, crm_list_dialer_queues |
| Communication and meetings | crm_draft_email, crm_find_conversations, crm_send_email, crm_send_sms, crm_book_meeting |
| Search and help | crm_search, crm_search_preview, crm_search_help |
The server does not provide payment processing, bulk record deletion, or tools to bypass team access.
Access and data
OAuth connects the assistant as your CRM user. Team-scoped tools check team access, and the Reports backend also enforces its role and plan requirements. Connecting an assistant does not create team membership.
Tool results can include CRM names, contact details, activity, and report data relevant to your request. Your assistant provider receives these results. Interactive panels use the host's MCP bridge to request data; they do not ask for your password or handle your OAuth token directly.
Read the Privacy Policy, Terms of Service, and Support Policy. Review your assistant provider's data policies before connecting customer information.
Troubleshooting
A login is required: start OAuth authentication in your assistant, complete CRM sign-in and consent, and return to the assistant. An unauthenticated request to the MCP endpoint receives an authentication challenge.
Access is denied: check that the connected CRM account belongs to the requested team. Reports also require the applicable analytics plan access. Member filtering is available only to team owners and admins.
The connection expired: reconnect through the assistant's OAuth flow. Do not paste tokens into chat or configuration files.
A tool or card is missing: refresh the custom MCP connection after a server update. Hosts may not support interactive MCP Apps, and published directories may hold new tools or UI until their review checks pass.
You need help: use the contact information on the Support Policy. Include the assistant name, tool name, and error message. Keep passwords, tokens, and private customer records out of support screenshots.