DevRev MCP server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is DevRev MCP server?

DevRev MCP server is a Model Context Protocol server designed for DevRev, enabling users to search and retrieve information using the DevRev APIs.

how to use DevRev MCP server?

To use the DevRev MCP server, you need to create an account on DevRev, import your data from existing sources, and generate an access token. Then, configure the server with your API key and run it using the provided commands.

key features of DevRev MCP server?

  • Search for information using the DevRev search API.
  • Retrieve detailed information about DevRev objects using their IDs.
  • Easy configuration for both published and unpublished servers.

use cases of DevRev MCP server?

  1. Integrating DevRev APIs into applications for data retrieval.
  2. Automating data import from platforms like Salesforce and Zendesk.
  3. Building custom applications that leverage DevRev's capabilities.

FAQ from DevRev MCP server?

  • How do I get the DevRev API key?

You can obtain the API key by signing up at DevRev and following the instructions to generate a personal access token.

  • Can I use DevRev MCP server on Windows?

Yes! The server can be configured and run on both MacOS and Windows.

  • What data sources can I import into DevRev?

You can import data from various sources including Salesforce and Zendesk.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
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.

8 hours ago