DevExpress Documentation MCP Server

Created By
DevExpress7 months ago
DevExpress documentation at your AI's fingertips.
Overview

what is DevExpress Documentation MCP Server?

DevExpress Documentation MCP Server is an AI-powered tool that allows developers to search DevExpress documentation using natural language queries across various technologies like Angular, Blazor, WPF, WinForms, ASP.NET, React, and Vue.

how to use DevExpress Documentation MCP Server?

To use the server, simply input your question or search query related to DevExpress technologies, and the server will provide instant code examples, implementation guidance, and step-by-step instructions.

key features of DevExpress Documentation MCP Server?

  • ✨ Natural language search across 20+ DevExpress product lines and 300,000+ help topics
  • 💻 Instant code examples and implementation patterns
  • 🤖 AI coding agent optimized with specialized tools and prompts
  • 📚 Access to comprehensive documentation for various technologies
  • ⚡ Accelerates development with contextual, accurate guidance

use cases of DevExpress Documentation MCP Server?

  1. Quickly finding code snippets for specific DevExpress components.
  2. Getting implementation patterns for integrating DevExpress UI components into applications.
  3. Accessing detailed documentation for troubleshooting and learning.

FAQ from DevExpress Documentation MCP Server?

  • Can I search for multiple technologies at once?

Yes! You can pass a list of technologies to search across them simultaneously.

  • Is there a limit to the number of queries I can make?

No, you can make as many queries as you need to find the information you require.

  • How accurate are the search results?

The search results are designed to be highly accurate, providing relevant snippets and guidance based on your queries.

Server Config

{
  "mcpServers": {
    "dxdocs": {
      "url": "https://api.devexpress.com/mcp/docs",
      "type": "http"
    }
  }
}
Project Info

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day 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.

3 hours ago
Crevio

2 days ago