About MCP Function App Tester
MCP Function App Tester is a TypeScript MCP server for developers testing Azure Function App endpoints through Cline. It supports common HTTP methods, request details, and configurable authentication.
Key features
- 01Tests endpoints with GET, POST, PUT, and DELETE
- 02Sets custom request headers
- 03Sends request bodies for POST and PUT
- 04Supports Basic, Bearer, and API key authentication
- 05Returns detailed response information
Use cases
- 01Test a local Function App endpoint
- 02Send authenticated API requests
- 03Inspect responses to POST or PUT requests
MCP support
Exposes tools for sending requests to Azure Function App endpoints to MCP clients such as Cline. The default base URL is http://localhost:7071/api.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMCP Function App Tester
A TypeScript-based MCP server that enables testing of Azure Function Apps through Cline. This tool allows you to test and interact with Function App endpoints directly from your development environment.
Installation
npm install dkmaker-mcp-function-app-tester
Features
- Test Function App endpoints with different HTTP methods
- Support for GET, POST, PUT, and DELETE requests
- Detailed response information
- Custom header support
- Request body handling for POST/PUT methods
- Authentication support:
- Basic Authentication (username/password)
- Bearer Token Authentication
- API Key Authentication (custom header)
Authentication
The server supports two authentication methods that can be configured via environment variables:
Basic Authentication
Set both environment variables to enable Basic Authentication:
AUTH_BASIC_USERNAME=your-username
AUTH_BASIC_PASSWORD=your-password
Bearer Token
Set this environment variable to enable Bearer Token authentication:
AUTH_BEARER=your-token
API Key
Set both environment variables to enable API Key authentication:
AUTH_APIKEY_HEADER_NAME=X-API-Key # The header name to use (e.g., X-API-Key, api-key, etc.)
AUTH_APIKEY_VALUE=your-api-key # The actual API key value
Note: Authentication precedence order:
- Basic Authentication (if username and password are set)
- Bearer Token (if token is set and Basic Auth is not configured)
- API Key (if header name and value are set, and no other auth is configured)
Usage
Once installed, you can use the Function App Tester through Cline. The server provides tools to test endpoints at the base URL: http://localhost:7071/api
Example usage:
// Test a GET endpoint
{
"method": "GET",
"endpoint": "/users"
}
// Test a POST endpoint with body
{
"method": "POST",
"endpoint": "/users",
"body": {
"name": "John Doe",
"email": "[email protected]"
}
}
// Test with custom headers
{
"method": "GET",
"endpoint": "/secure/data",
"headers": {
"Authorization": "Bearer token123"
}
}
Development
- Clone the repository:
git clone https://github.com/dkmaker/mcp-function-app-tester.git
cd mcp-function-app-tester
- Install dependencies:
npm install
- Build the project:
npm run build
For development with auto-rebuild:
npm run watch
License
This project is licensed under the MIT License - see the LICENSE file for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.