SugarCRM MCP for AI. Manage accounts, contacts, and leads directly from your agent.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
SugarCRM provides an MCP Server that lets your AI agent talk directly to your enterprise CRM instance. It gives you ten tools—from listing specific accounts to running bulk updates across modules.
Manage customer records, track relationships, and pull account history without ever leaving your chat interface.
What AI agents can do with SugarCRM (Enterprise CRM & Customer Success API) Automation
Bulk request
Sends multiple API calls at once, letting you process many records in a single operation.
Count records
Counts how many records match a specific filter inside any CRM module.
Create record
Adds a brand new record into any designated SugarCRM module.
Use list_records to pull targeted lists of accounts or contacts by applying complex JSON filters.
Retrieve details for one specific record using get_record, or modify its data with update_record and delete_record.
Generate new records in any module via create_record, or execute massive changes across multiple entries using bulk_request.
Understand the full client picture by listing related records with list_related_records, or clean up data by calling unlink_record.
Determine how many records match specific criteria instantly using count_records for quick reporting metrics.
Ask an AI about this
Waiting for input…
What AI agents can do with SugarCRM (Enterprise CRM & Customer Success API) - 10 Tools
Use these ten tools to perform every core function in SugarCRM: filtering, creating, updating, and mapping relationships between all your records.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using SugarCRM (Enterprise CRM & Customer Success API) on VinkiusBulk Request
Sends multiple API calls at once, letting you process many records in a single operation.
Count Records
Counts how many records match a specific filter inside any CRM module.
Create Record
Adds a brand new record into any designated SugarCRM module.
Delete Record
Permanently removes a specific, identified SugarCRM record from the system.
Get Record
Pulls all data for one single, known SugarCRM record ID.
Link Record
Establishes a relationship between two existing records in the CRM.
List Records
Retrieves a list of filtered records from any module, supporting complex JSON query filters.
List Related Records
Finds and lists all records connected to a specific existing record ID.
Unlink Record
Removes an established relationship link between two records, keeping the data...
Update Record
Changes specific fields on an existing SugarCRM record using its ID.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The SugarCRM integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with SugarCRM (Enterprise CRM & Customer Success API), then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by SugarCRM. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Juggling tabs to build a client profile shouldn't take ten clicks., Solved with Vinkius AI Gateway
Right now, understanding one customer means jumping between the Account tab, the Contacts list, the Activity History log, and maybe even an associated Opportunity record. You copy IDs here, paste them there, and click 'View Details' until you hit a wall of context switching.
With this MCP server, you just ask your agent: 'Show me everything related to Acme Corp.' The agent runs `list_related_records` across modules and gives you the full picture—the history, the contacts, the status—all in one coherent response.
Using SugarCRM's tools with the sugarcrm-enterprise-crm-customer-success-api MCP Server
Manual updates require logging into the system, finding the specific record ID, navigating to the right field, and clicking save. This process is slow, prone to human error, and kills momentum.
Now, you tell your agent: 'Update Lead 456's status to Qualified.' It runs `update_record` instantly. The data changes, no login required, and the confirmation comes back in your chat.
What your AI can actually do with this
You connect your AI agent straight into your SugarCRM instance, giving it full read and write access across all modules. This server exposes ten tools that let you manage every piece of customer data using natural language commands.
To pull a focused list of accounts or contacts, use list_records. You can apply complex JSON filters to narrow down the results, so your agent only pulls exactly what you need from any module. If you just want the details for one specific record ID, get_record grabs all that data instantly.
For quick reporting metrics, you'll use count_records; it tells you immediately how many records match a set of criteria.
When you need to map out client relationships, list_related_records finds and lists every existing record connected to one specific ID. You can establish new connections by calling link_record, or if the relationship is wrong, unlink_record removes the link while keeping both data points intact.
Changing records is straightforward. To add a brand-new entry into any designated module, you use create_record. If an existing record needs tweaks—say, updating a phone number or changing a status—update_record lets your agent change specific fields using the record's ID. You can permanently wipe data by running delete_record, which removes that identified SugarCRM record from the system.
When you gotta make big changes across multiple entries, don’t bother with ten separate calls; use bulk_request. This tool sends multiple API calls at once, letting your agent process dozens of records in a single operation. To wrap up all this functionality, remember that you can also pull targeted lists using the foundational list_records and run counts to verify how many items match those filters.
019e5d5b-3ce1-702c-afd3-6133c743cbbc 
Here's how it actually works
The bottom line is you use natural language prompts; the server does the heavy API lifting.
First, subscribe to the server and plug in your SugarCRM Instance URL, Username, and Password.
Next, tell your AI agent exactly what you need. For example: 'List all accounts associated with John Doe.'
The agent translates that into a specific tool call (e.g., list_related_records), runs it against your CRM data, and sends the results back to your chat.
Who is this actually for?
Anyone who spends too much time switching between their CRM and their documentation. This is for the Sales Rep who hates leaving the chat window to update a lead status, or the CSM drowning in account history that's scattered across five different tabs.
Retrieves full account histories and related contact details instantly. They use list_related_records to build a single timeline of client interactions.
Updates lead statuses or logs interaction notes in bulk without context-switching. They rely on bulk_request for high throughput.
Needs to quickly size a problem space. They use count_records and advanced JSON filtering via list_records instead of running manual reports.
What Changes When You Connect
Stop manual data lookups. Use list_related_records to instantly pull every contact or account touchpoint tied to a single client ID in one request.
Handle large-scale cleanups fast. The bulk_request tool lets you update status fields across hundreds of leads simultaneously, bypassing tedious individual calls.
Get immediate metrics without running reports. Just ask the agent to count records using count_records, and it gives you the exact number right now.
Keep your work in context. Instead of logging into SugarCRM, use the agent's ability to run get_record and get the data straight into your chat window.
Maintain clean data relationships. Use link_record or unlink_record directly via prompts, ensuring your CRM structure is accurate without needing manual admin intervention.
See it in action
The Account Audit
A CSM needs to understand why a client's billing address changed. They ask their agent to 'Show me all records related to Account ID X.' The agent uses list_related_records and pulls the account history, showing the exact change date and user.
Lead Status Blitz
An SDR finishes a big outreach day. Instead of logging into SugarCRM for 50 leads, they prompt: 'Update all these 50 IDs to Stage 3.' The agent runs bulk_request and updates every status in seconds.
Data Integrity Check
A data analyst suspects some contacts are incorrectly linked. They ask the agent to 'Check for unlinked accounts with more than five contacts.' The agent uses a combination of list_records and count_records to flag potential data problems.
Mass Deletion Cleanup
An admin needs to clear out all test records from a specific module. They prompt: 'Delete all records in the Test Leads module.' The agent executes delete_record safely, keeping the main data clean.
The honest tradeoffs
Serial API calls
Trying to update 20 lead statuses by running 'update_record' twenty separate times. It takes forever and fails if one call hiccups.
Use bulk_request. Feed the agent a list of IDs and the new status, then run one single bulk request. It handles all 20 updates in one go.
Guessing relationships
Thinking two records are related just because they share a name. You might lose data or create bad links.
Don't guess. Use list_related_records. This tool checks the actual established links in SugarCRM, giving you verifiable facts about connections.
Forgetting filters
Asking 'List all accounts.' You get thousands of irrelevant records and have to sift through them manually.
Always specify. Use list_records with complex JSON filtering, like 'List accounts created in Q3 that are marked as Enterprise'—no fluff results.
When It Fits, When It Doesn't
Use this server if your job involves constantly reading, writing, or mapping data between records in SugarCRM. It excels when you need to read account history (use list_related_records) and then immediately act on it by updating a status (using update_record). Don't use it if you just need general CRM documentation or training material—those are separate tools. If your goal is pure data visualization (like running a BI dashboard), that's outside the scope; this server handles transactional, real-time record manipulation and relationship management only.
Questions you might have
How do I get a list of accounts using the list_records tool? +
You prompt the agent to use list_records and specify the module ('Accounts') along with your required JSON filters. The system runs it, returning the records that match your criteria.
Can I update many leads at once using bulk_request? +
Yes. You gather all the IDs and the field changes you want to make, then send a single prompt asking the agent to run bulk_request. This is far faster than individual updates.
What is the difference between get_record and list_records? +
get_record requires one specific ID and returns only that record's data. list_records allows you to query a set of records using filters, giving you multiple results.
How do I establish a link between two accounts? Do I use link_record? +
You tell the agent to use link_record. You just need to provide the IDs for both existing records, and it handles creating the necessary relationship in SugarCRM.
How do I use advanced filters when calling list_records? +
You must pass complex filtering criteria using a JSON object in the parameters. This allows you to query specific data points, like finding all Accounts owned by a certain user or created within a date range, far beyond simple module listing.
What happens if I try to use link_record with an invalid Account ID? +
The API will return an error stating that the provided record ID does not exist. You must verify both the source and target IDs before running a link request; otherwise, the operation fails.
Is it better to use bulk_request or multiple individual updates with update_record? +
Always use bulk_request when performing several similar actions. It drastically reduces API overhead and speeds up processing time by grouping those calls into a single, efficient transaction.
If I delete_record, does it affect related records that were linked via link_record? +
The system handles deletion based on your instance's configured rules. Generally, deleting a core record might break associated links; always check the resulting data to confirm referential integrity before running delete operations.
Can I filter records by specific criteria like account name? +
Yes! Use the list_records tool with a JSON filter string. For example, you can pass [{"name": "Nelson Inc"}] to find specific accounts matching that name.
How do I see all opportunities linked to a specific account? +
Use the list_related_records tool by providing the primary module (Accounts), the record ID, and the link name (e.g., 'opportunities').
Is it possible to get a total count of records in a module? +
Absolutely. The count_records tool allows you to retrieve the total number of records in any module, optionally filtered by specific conditions.
We've already built the connector for SugarCRM. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.