mcp-server-salesforce MCP server

Created By
kazuki1213a year ago
Overview

what is mcp-server-salesforce?

The mcp-server-salesforce is a Model Context Protocol server implementation designed for interacting with Salesforce, allowing users to manage notes and generate summaries.

how to use mcp-server-salesforce?

To use the mcp-server-salesforce, install the server and configure it according to your environment. You can add notes using the provided tool and summarize them with the available prompt.

key features of mcp-server-salesforce?

  • Custom note storage system with a unique note:// URI scheme.
  • Ability to create summaries of stored notes with adjustable detail levels.
  • Tools for adding new notes and notifying clients of changes.

use cases of mcp-server-salesforce?

  1. Managing and summarizing notes for Salesforce interactions.
  2. Storing and retrieving notes efficiently using a custom URI scheme.
  3. Facilitating quick access to important information through summarized notes.

FAQ from mcp-server-salesforce?

  • What is the purpose of the mcp-server-salesforce?

It serves as a server for managing notes and generating summaries in the context of Salesforce.

  • How do I add a note?

Use the 'add-note' tool with the required name and content arguments.

  • Can I customize the summary detail level?

Yes, you can specify a 'style' argument to control the detail level of the summary.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kazuki1213
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago