DNN API Server (.NET C# Version)

Created By
sachatrauwaena year ago
Overview

what is DNN API Server?

DNN API Server is a Model Context Protocol (MCP) server for the DNN Platform, implemented in C# using .NET. It allows developers to interact with the DNN Platform through its APIs.

how to use DNN API Server?

To use the DNN API Server, configure it with your DNN installation API URL and credentials, then build and run the server using .NET commands.

key features of DNN API Server?

  • Authentication with DNN API
  • Host management tools
  • Portal management tools
  • Support for site configuration via environment variables or JSON file
  • Easily extensible using MCP SDK attributes

use cases of DNN API Server?

  1. Managing DNN host settings and cache.
  2. Retrieving and listing portal details.
  3. Extending server functionality by adding new tools.

FAQ from DNN API Server?

  • What are the requirements to run DNN API Server?

You need .NET 7.0 or higher and a DNN Platform instance.

  • How do I configure the server?

The server can be configured using environment variables or a JSON configuration file.

  • Can I add new tools to the server?

Yes! You can add new methods to the DnnTools class and decorate them with MCP attributes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sachatrauwaen
Star
0
Language
C#
License
MIT license
Tags

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
Tavily Mcp
@tavily-ai

JavaScript
a year ago