Azure Function Apps MCP server

The MCP Function App Tester is a TypeScript-based MCP server that allows you to test Azure Function App endpoints through Cline. It provides a convenient way to interact with Function App endpoints directly from your development environment without leaving your workflow.

Installation

Install the package using npm:

npm install dkmaker-mcp-function-app-tester

Features

• Test Function App endpoints with different HTTP methods (GET, POST, PUT, DELETE)
• Get detailed response information
• Add custom headers to your requests
• Send request bodies for POST/PUT methods
• Multiple authentication options

Authentication Options

The server supports three authentication methods configurable via environment variables:

Basic Authentication

Set both of these 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
AUTH_APIKEY_VALUE=your-api-key     # The actual API key value

Note: Authentication follows this precedence order:

1. Basic Authentication (if username and password are set)
2. Bearer Token (if token is set and Basic Auth is not configured)
3. API Key (if header name and value are set, and no other auth is configured)

Usage Examples

After installation, you can use the Function App Tester through Cline. The server lets you test endpoints at the base URL: http://localhost:7071/api

Testing a GET Endpoint

{
  "method": "GET",
  "endpoint": "/users"
}

Testing a POST Endpoint with Request Body

{
  "method": "POST",
  "endpoint": "/users",
  "body": {
    "name": "John Doe",
    "email": "[email protected]"
  }
}

Using Custom Headers

{
  "method": "GET",
  "endpoint": "/secure/data",
  "headers": {
    "Authorization": "Bearer token123"
  }
}

Testing Other HTTP Methods

The server supports all common HTTP methods, including PUT and DELETE:

{
  "method": "PUT",
  "endpoint": "/users/123",
  "body": {
    "name": "Updated Name",
    "email": "[email protected]"
  }
}

{
  "method": "DELETE",
  "endpoint": "/users/123"
}

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.