MCP Function App Tester

Created By
dkmakera year ago
A MCP Server to test local development of function app apis
Overview

What is MCP Function App Tester?

MCP Function App Tester is a TypeScript-based server designed to facilitate the testing of Azure Function Apps directly from your development environment.

How to use MCP Function App Tester?

To use the MCP Function App Tester, install it via npm and interact with Function App endpoints using the provided tools through Cline. The base URL for testing is http://localhost:7071/api.

Key features of MCP Function App Tester?

  • Test Function App endpoints with various HTTP methods (GET, POST, PUT, DELETE)
  • Detailed response information
  • Custom header support
  • Request body handling for POST/PUT methods
  • Multiple authentication methods: Basic, Bearer Token, and API Key

Use cases of MCP Function App Tester?

  1. Testing API endpoints during local development.
  2. Validating the functionality of Azure Function Apps.
  3. Ensuring proper authentication mechanisms are in place.

FAQ from MCP Function App Tester?

  • What authentication methods are supported?

The server supports Basic Authentication, Bearer Token, and API Key authentication.

  • How do I install the MCP Function App Tester?

You can install it using npm with the command: npm install dkmaker-mcp-function-app-tester.

  • Can I test different HTTP methods?

Yes! The tool supports GET, POST, PUT, and DELETE requests.

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

Recommend Servers

View All
Fairrate

a day ago
Klave Mcp
@juny-klave

@juny-klave/mcp MCP server that gives Claude the ability to negotiate prices on your behalf — autonomously, privately, and with cryptographic proof of the outcome. What it does KLAVE connects Claude to a bilateral negotiation engine. You describe what you want in plain English; Claude calls KLAVE, runs the negotiation through multiple rounds, and reports back with the settled price and a ZK proof reference. Your ceiling is cryptographically bound to the authorization token and never appears in any response — the seller never sees your budget. What You Can Negotiate Anything with a price. KLAVE does not require pre-existing listings, platform partnerships, or pre-seeded scenarios. If it has an asking price and you have a ceiling, KLAVE can negotiate it. Freight and logistics "Negotiate 200 FEU containers Shanghai to Rotterdam. They're asking $2,806. My ceiling is $2,700." Software and SaaS "Get me a better price on this CRM license. 500 seats, they want $75,000 annually. I won't go above $58,000." Employment and contracts "A contractor is asking $185/hour for a 6-month engagement. My budget is $150/hour. Negotiate it." Real estate "Negotiate our office lease renewal. Landlord wants $42/sqft. We need to be at $35 or below." Legal and settlement "Negotiate a settlement. The other party is asking $250,000. My ceiling is $180,000." Any bilateral negotiation "They're asking [X]. I won't pay more than [Y]. Negotiate." Prerequisites Node.js 18+ Claude Desktop or Claude Code A KLAVE API key — get one at https://klave-platform.vercel.app/docs Install in Claude Desktop Add to ~/Library/Application Support/Claude/claude_desktop_config.json: { "mcpServers": { "klave": { "command": "npx", "args": [ "-y", "mcp-remote", "https://klave1-production.up.railway.app/mcp/sse", "--header", "x-api-key:YOUR_API_KEY" ] } } } Replace YOUR_API_KEY with your key from https://klave-platform.vercel.app/docs Install in Claude Code claude mcp add klave \ --transport sse \ "https://klave1-production.up.railway.app/mcp/sse" \ --header "x-api-key:YOUR_API_KEY" Run locally (stdio) git clone https://github.com/juny-klave/klave-mcp.git cd klave-mcp npm install npm run build Then point Claude Desktop at the local build: { "mcpServers": { "klave": { "command": "node", "args": ["/absolute/path/to/klave-mcp/dist/index.js"], "env": { "KLAVE_API_URL": "https://klave1-production.up.railway.app", "KLAVE_API_KEY": "YOUR_API_KEY" } } } } The 4 tools Tool What it does klave_negotiate Start a negotiation — any subject, any industry, any price range klave_advance Advance one round — call in a loop until SETTLED or TERMINATED klave_status Get current state and full round history at any time klave_verify Get the ZK proof confirming the settlement was conducted fairly Tool sequence klave_negotiate ← describe what you're negotiating and your ceiling klave_advance (loop) ← advance round by round until SETTLED klave_status ← check progress at any time klave_verify ← get cryptographic proof after settlement Privacy guarantees Your ceiling (ceiling_price) is passed to the negotiation engine and never appears in any tool response. The seller's floor price is derived server-side and never a field in any API response. leaks_detected in verify responses is sourced from the server — never hardcoded. Every negotiation generates an auditable ZK proof. Environment variables (local mode) Variable Default Description KLAVE_API_URL https://klave1-production.up.railway.app KLAVE REST API base URL KLAVE_API_KEY (empty) API key TRANSPORT stdio stdio (Claude Desktop/Code) or http (remote/SSE) PORT 3002 HTTP port when TRANSPORT=http Getting an API key Sign up at https://klave-platform.vercel.app/docs Developer SDK If you're building an agent that needs to authorize negotiation programmatically, see the KLAVE SDK (@juny-klave/sdk). License MIT

14 hours ago
Fast.io
@MediaFire

12 hours ago