DevRev MCP Serverofficial
A
securityA
licenseA
qualityA Model Context Protocol server that enables searching, retrieving, creating, and updating issues and tickets using DevRev APIs.
Last updated -
16
5
Python
MIT License
Salesforce is a cloud-based customer relationship management (CRM) platform that helps businesses connect with customers, partners, and employees through integrated applications for sales, service, marketing, and more.
Why this server?
Allows importing data from Salesforce into DevRev as a source for the MCP server.
Why this server?
Allows LLMs to interact with Salesforce data through SOQL queries, SOSL searches, and provides tools for retrieving metadata, managing records (create, read, update, delete), executing Tooling API requests, running Apex REST requests, and making direct REST API calls to Salesforce.
Why this server?
Enables interaction with Salesforce CRM APIs through URL restrictions and secure credential management for marketing team access.
Why this server?
Provides comprehensive access to Salesforce data and metadata, enabling object and field management, schema exploration, data querying with relationship support, record creation/modification, cross-object searching, and custom object development - all using the Salesforce API.
Why this server?
Enables interaction with Salesforce data through SOQL queries, SOSL searches, and various operations including retrieving metadata, managing records (create, read, update, delete), executing Tooling API requests, running Apex REST requests, and making direct REST API calls to Salesforce.
Why this server?
Enables querying, modifying, and managing Salesforce objects and records, with capabilities for object/field management, schema information retrieval, data querying with relationship support, record manipulation (insert, update, delete), and cross-object searching using SOSL.
Why this server?
Provides tools for interacting with Salesforce data and metadata, enabling object search, schema retrieval, record querying, data manipulation (insert, update, delete, upsert), custom object/field management, and cross-object searching using SOSL.
Why this server?
Provides comprehensive tools for Salesforce B2C Commerce Cloud (SFCC) development including log analysis and monitoring, SFCC API documentation querying, system object definitions access, and best practices guides for OCAPI hooks, SCAPI hooks, SFRA controllers, and custom endpoints
Why this server?
Listed as a supported data source that can be accessed through the CData JDBC driver, allowing for data retrieval from Salesforce CRM platform.
Why this server?
Allows interaction with Salesforce through its REST API using jsforce, including executing SOQL queries, retrieving object metadata, and creating, updating, and deleting records in Salesforce.
Why this server?
Wraps the Salesforce CLI to provide access to Salesforce org functionality including organization management, Apex code execution, data querying, schema exploration, and deployment capabilities.
Why this server?
Enables interaction with Salesforce data through SOQL queries, SOSL searches, object metadata retrieval, record operations (create, read, update, delete), Tooling API requests, Apex REST requests, and direct REST API calls.
Why this server?
Listed as a supported data source in the compatibility table, enabling access to Salesforce data.
Why this server?
Listed as a supported data source for integration through the CData JDBC driver.
Why this server?
Provides read access to Salesforce CRM data through SQL interfaces, enabling natural language querying of customer relationship management information.
Why this server?
Provides access to Salesforce CRM data through SQL queries.
Why this server?
Provides read-only access to Salesforce CRM data.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for data access.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver, enabling data querying capabilities.
Why this server?
Listed as a supported data source that can be accessed through the CData JDBC driver integration.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for querying Salesforce data.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for retrieving data.
Why this server?
Provides SQL-based access to Salesforce data, enabling retrieval of CRM information through natural language questions.
Why this server?
Listed as a supported data source that can be queried through the MCP server.
Why this server?
Listed as a supported data source for integration, enabling access to Salesforce CRM data through the CData JDBC Driver.
Why this server?
Allows access to Salesforce CRM data through SQL interfaces.
Why this server?
Provides SQL access to Salesforce CRM data, including accounts, contacts, opportunities, and custom objects.
Why this server?
Listed as a supported data source for integration, allowing access to Salesforce CRM data.
Why this server?
Provides read-only access to Salesforce data by exposing tables as relational SQL models, allowing retrieval of live data through simple MCP queries.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver.
Why this server?
Provides access to Salesforce data through SQL models, allowing querying of live information such as account details, opportunities, and other Salesforce objects.
Why this server?
Enables querying Salesforce data sources by exposing them as relational SQL models that can be accessed through natural language queries.
Why this server?
Enables querying of Salesforce CRM and platform data through SQL interfaces.
Why this server?
Enables SQL-based access to Salesforce CRM data, including accounts, contacts, and opportunities.
Why this server?
Provides read-only SQL access to Salesforce CRM data, including accounts, contacts, opportunities, and custom objects.
Why this server?
Offers SQL-based access to Salesforce data, allowing queries across objects like Accounts, Opportunities, and Contacts through a relational interface.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver framework.
Why this server?
Provides read-only access to Salesforce data through SQL models, allowing queries of Salesforce data through natural language requests.
Why this server?
Integration with Salesforce demonstrated through a vulnerable 'Salesforce Connector' that can be exploited through server name collision attacks.
Why this server?
Enables comprehensive querying of Salesforce CRM data including accounts, contacts, opportunities, cases, and custom objects through SQL operations.
Why this server?
Provides read-only access to Salesforce CRM data through SQL queries, enabling retrieval of leads, opportunities, accounts, and sales information
Why this server?
Provides read-only access to Salesforce CRM data through SQL queries, enabling retrieval of contacts, leads, opportunities, and sales data
Why this server?
Enables querying of Salesforce CRM data including accounts, contacts, opportunities, leads, and sales pipeline information.
Why this server?
Allows querying Salesforce CRM data including accounts, contacts, opportunities, and custom objects through SQL
Why this server?
Enables querying Salesforce CRM data including accounts, contacts, opportunities, and custom objects through SQL operations.
Why this server?
Enables SQL-based access to Salesforce CRM data, allowing querying of leads, opportunities, accounts, and sales pipeline information
Why this server?
Enables access to Salesforce CRM data including accounts, contacts, opportunities, leads, and custom objects through SQL-like queries.
Why this server?
Allows comprehensive SQL querying of Salesforce CRM data including accounts, contacts, opportunities, and custom objects.
Why this server?
Allows comprehensive querying of Salesforce CRM data including accounts, contacts, opportunities, and custom objects
Why this server?
Provides comprehensive access to Salesforce CRM data including accounts, contacts, opportunities, and custom objects through SQL operations
Why this server?
Enables comprehensive querying of Salesforce CRM data including leads, opportunities, accounts, and custom objects through SQL operations
Why this server?
Enables querying Salesforce CRM data including accounts, contacts, opportunities, and custom objects
Why this server?
Provides comprehensive access to Salesforce CRM data including accounts, contacts, opportunities, and custom objects
Why this server?
Allows querying of Salesforce CRM data including accounts, opportunities, contacts, and sales information
Why this server?
Allows access to Salesforce CRM data including accounts, contacts, opportunities, and custom objects through SQL queries
Why this server?
Allows SQL-based access to Salesforce CRM data including accounts, contacts, opportunities, and custom objects
Why this server?
Enables SQL queries against Salesforce CRM data including accounts, contacts, opportunities, and custom objects through CData's JDBC driver
Why this server?
Enables comprehensive querying of Salesforce CRM data including accounts, opportunities, and customer information
Why this server?
Allows SQL-based querying of Salesforce CRM data, providing access to leads, accounts, opportunities, contacts, and sales pipeline information.
Why this server?
Allows comprehensive querying of Salesforce CRM data including accounts, contacts, opportunities, and custom objects.
Why this server?
Provides access to Salesforce CRM data including accounts, contacts, opportunities, and sales information through SQL queries.
Why this server?
Allows SQL querying of Salesforce CRM data including accounts, contacts, opportunities, and sales pipeline information.
Why this server?
Enables comprehensive querying of Salesforce CRM data including leads, opportunities, accounts, and custom objects
Why this server?
Provides read-only access to Salesforce Pardot data through SQL queries, enabling retrieval of marketing automation data including prospects, campaigns, and analytics via natural language questions
Why this server?
Allows comprehensive querying of Salesforce CRM data including leads, opportunities, accounts, and custom objects
Why this server?
Allows querying Salesforce CRM data through SQL interface, providing access to leads, opportunities, accounts, and customer information.
Why this server?
Provides tools for querying Salesforce CRM platform data including contacts, accounts, opportunities, and sales information
Why this server?
Provides SQL-based access to Salesforce CRM data including accounts, contacts, opportunities, and sales information
Why this server?
Listed as a supported data source for querying Salesforce CRM data including accounts, contacts, opportunities, and more.
Why this server?
Provides SQL access to Salesforce objects, records, and relationships.
Why this server?
Allows SQL-based access to Salesforce CRM data.
Why this server?
Listed as a supported data source for integration, allowing access to Salesforce data through the MCP server.
Why this server?
Allows querying Salesforce CRM objects, records, and relationship data through SQL.
Why this server?
Enables querying Salesforce CRM data including accounts, contacts, and opportunities through SQL
Why this server?
Allows querying of Salesforce CRM data including contacts, accounts, opportunities and custom objects through relational SQL models.
Why this server?
Enables SQL-based querying of Salesforce CRM data.
Why this server?
Allows querying of Salesforce data by exposing it as relational SQL models through the CData JDBC Driver.
Why this server?
Enables access to Salesforce CRM data through relational SQL models, supporting table discovery, column information retrieval, and SQL query execution.
Why this server?
Enables importing data from Salesforce into DevRev for search and retrieval via the DevRev APIs.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver.
Why this server?
Provides SQL query capabilities for Salesforce CRM data, including accounts, opportunities, and contacts.
Why this server?
Allows querying Salesforce objects, records, and CRM data through SQL interfaces.
Why this server?
Provides access to Salesforce CRM data through SQL-based tools for listing tables, retrieving column information, and executing SELECT queries.
Why this server?
Provides access to Salesforce CRM data including accounts, contacts, and opportunities.
Why this server?
Provides access to SAS Data Sets containing Salesforce data through SQL queries.
Why this server?
Provides access to Salesforce CRM data by exposing it as queryable SQL tables through the MCP server.
Why this server?
Enables querying of Salesforce CRM data including contacts, opportunities, and accounts through SQL interfaces.
Why this server?
Allows accessing Salesforce CRM data through SQL queries.
Why this server?
Provides SQL-based access to Salesforce CRM data, enabling queries against contacts, opportunities, accounts, and other Salesforce objects.
Why this server?
Enables SQL-based access to Salesforce CRM data including contacts, opportunities, and accounts.
Why this server?
Allows read-only access to Salesforce CRM data via SQL models.
Why this server?
Provides read-only access to Salesforce CRM data, enabling queries for accounts, contacts, opportunities, and other CRM objects.
Why this server?
Provides read-only access to Salesforce CRM data including accounts, opportunities, and customer information
Why this server?
Enables interaction with Salesforce CRM, allowing for contact management operations such as creating, retrieving, and listing contacts.
Why this server?
Enables SQL-based querying of Salesforce CRM data, including accounts, contacts, opportunities, and custom objects.
Why this server?
Enables SQL-based access to Salesforce CRM data, supporting querying of accounts, contacts, opportunities, and custom objects.
Why this server?
Enables querying, modifying, and managing Salesforce objects and records. Provides tools for searching objects, retrieving schema information, executing complex data queries, exploring relationships between objects, accessing picklist values, filtering field types, retrieving validation rules, and managing debug logs.
Why this server?
Provides read-only access to Salesforce Einstein data through SQL-based queries, allowing for retrieval of tables, columns, and execution of SELECT queries against live Salesforce Einstein data.
Why this server?
Enables querying and analyzing sales and customer data from Salesforce through Coupler.io data flows.
Why this server?
Enables querying Salesforce CRM data including leads, opportunities, accounts, and sales information through SQL operations.
Why this server?
Allows querying Salesforce CRM data through SQL operations, providing access to leads, opportunities, accounts, and sales analytics.
Why this server?
Provides access to Salesforce CRM data including accounts, contacts, opportunities, and custom objects.
Why this server?
Allows read-only access to Salesforce CRM data including contacts, opportunities, and accounts.
Why this server?
Listed as a supported data source for integration with the MCP server, allowing access to Salesforce data.
Why this server?
Offers read-only access to Salesforce CRM data including contacts, opportunities, and accounts.
Why this server?
Provides access to Salesforce data through SQL-like queries, allowing retrieval of live information from Salesforce objects like opportunities, accounts, contacts, and other custom entities.
Why this server?
Allows querying of live Salesforce data through the CData JDBC driver, exposing Salesforce tables as relational SQL models that can be accessed through natural language queries.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver
Why this server?
Allows querying Salesforce CRM data through SQL interfaces.
Why this server?
Provides SQL querying of Salesforce CRM data, including leads, accounts, opportunities, contacts, and sales analytics for customer relationship management.
Why this server?
Provides SQL access to Salesforce CRM data, enabling queries on contacts, leads, opportunities, and customer relationship information.
Why this server?
Enables querying Salesforce data through the CData JDBC driver, mentioned in examples for configuration and usage scenarios.
Why this server?
Allows access to CRM data from Salesforce including accounts, contacts, opportunities, and custom objects.
Why this server?
Enables comprehensive read-only access to Salesforce CRM data, allowing queries on leads, opportunities, accounts, contacts, and sales analytics.
Why this server?
Provides comprehensive access to Salesforce CRM data including accounts, contacts, opportunities, and sales analytics through SQL queries.
Why this server?
Enables SQL access to Salesforce CRM data including leads, opportunities, accounts, and sales analytics
Why this server?
Enables access to Salesforce CRM data, including accounts, contacts, and opportunities through SQL queries.
Why this server?
Enables read-only access to Salesforce data through natural language queries rather than SQL commands.
Why this server?
Provides comprehensive access to Salesforce CRM data including accounts, contacts, opportunities, and business processes.
Why this server?
Provides SQL-based access to Salesforce CRM data including accounts, contacts, opportunities, and custom objects.
Why this server?
Provides read-only access to Salesforce CRM data including accounts, contacts, opportunities, and custom objects through SQL queries.
Why this server?
Allows querying Salesforce CRM data through SQL interfaces, providing access to leads, contacts, opportunities, and other sales information.
Why this server?
Allows SQL-based queries of Salesforce CRM data.
Why this server?
Included in the list of supported sources for data retrieval through the MCP server.
Why this server?
Enables querying of Salesforce CRM data including leads, opportunities, accounts, and customer relationship information.
Why this server?
Provides SQL-based access to Salesforce CRM data including accounts, contacts, opportunities, and custom objects.
Why this server?
Provides read-only access to Salesforce CRM data, allowing retrieval of accounts, contacts, opportunities, and custom object information through natural language queries.
Why this server?
Provides comprehensive SQL access to Salesforce CRM data including leads, opportunities, accounts, and sales analytics
Why this server?
Enables SQL-based querying of Salesforce CRM data.
Why this server?
Listed as a supported data source that can be accessed through the MCP server.
Why this server?
Enables SQL-based querying of Salesforce CRM data, providing access to accounts, contacts, opportunities, and customer relationship management information
Why this server?
Enables interaction with Salesforce data and metadata using natural language, allowing users to query records, manage data (create, update, delete), explore data structure, create/delete custom objects and fields, create custom tabs and apps, and connect to Salesforce API endpoints.
Why this server?
Provides access to Salesforce Marketing data through SQL models, allowing querying of marketing campaigns, contacts, and other Salesforce Marketing entities.
Why this server?
Enables access to Salesforce CRM data, allowing queries of accounts, contacts, opportunities, leads, and customer relationship information.
Why this server?
Listed as a supported data source that can be accessed through the MCP server interface, allowing retrieval of Salesforce data through SQL queries.
Why this server?
Listed as a supported data source that can be accessed through CData JDBC Driver and exposed via the MCP server.
Why this server?
Enables interaction with Salesforce data through SOQL queries, SOSL searches, and CRUD operations. Provides tools for accessing metadata, executing Tooling API requests, making Apex REST calls, and performing direct REST API calls to Salesforce.
Why this server?
Provides natural language querying capabilities for Salesforce data with intelligent SOQL/SOSL generation, cross-object search, data manipulation operations (DML), and automated field resolution. Optimized for wholesale distribution systems with support for inventory management, order processing, and supply chain operations.
Why this server?
Allows interaction with Salesforce through its REST API, providing capabilities to execute SOQL queries, retrieve object metadata, create/update/delete records, and access real-time data from a Salesforce instance.
Why this server?
Allows executing SOQL queries against Salesforce data, retrieving and processing Salesforce records, and interacting with Salesforce orgs using authenticated connections.
Why this server?
Enables data pipeline creation from Salesforce as a source connector to extract CRM data, leads, contacts, and other Salesforce objects
Why this server?
Mentioned as a potential CRM integration for business data retrieval and analysis
Why this server?
Provides tools to interact with the Salesforce Agentforce API, allowing authentication, session creation, and message exchange with Agentforce agents through the Salesforce platform.