Back to MCP directory
publicPublicdnsLocal runtime

mcp-azure-tablestorage

通过Cline直接与Azure表存储进行交互。此工具允许您查询和管理Azure存储表中的数据。

article

README

Azure TableStore MCP Server

License: MIT

A TypeScript-based MCP server that enables interaction with Azure Table Storage directly through Cline. This tool allows you to query and manage data in Azure Storage Tables.

mcp-azure-tablestorage MCP server

Features

  • Query Azure Storage Tables with OData filter support
  • Get table schemas to understand data structure
  • List all tables in the storage account
  • Detailed error handling and response information
  • Simple configuration through connection string

Installation

Local Development Setup

  1. Clone the repository:
git clone https://github.com/dkmaker/mcp-azure-tablestorage.git
cd mcp-azure-tablestorage
  1. Install dependencies:
npm install
  1. Build the server:
npm run build

NPM Installation

You can install the package globally via npm:

npm install -g dkmaker-mcp-server-tablestore

Or run it directly with npx:

npx dkmaker-mcp-server-tablestore

Note: When using npx or global installation, you'll still need to configure the AZURE_STORAGE_CONNECTION_STRING environment variable.

Installing in Cline

To use the Azure TableStore server with Cline, you need to add it to your MCP settings configuration. The configuration file is located at:

Windows: %APPDATA%CodeUserglobalStoragesaoudrizwan.claude-devsettingscline_mcp_settings.json

Add the following to your configuration:

{
  "mcpServers": {
    "tablestore": {
      "command": "node",
      "args": ["C:/path/to/your/mcp-azure-tablestorage/build/index.js"],
      "env": {
        "AZURE_STORAGE_CONNECTION_STRING": "your_connection_string_here"  // Required: Your Azure Storage connection string
      }
    }
  }
}

Replace C:/path/to/your/mcp-azure-tablestorage with the actual path where you cloned the repository.

Configuration

The server requires the following environment variable:

  • AZURE_STORAGE_CONNECTION_STRING: Your Azure Storage account connection string

Usage in Cline

⚠️ IMPORTANT SAFETY NOTE: The query_table tool returns a limited subset of results (default: 5 items) to protect the LLM's context window. DO NOT increase this limit unless explicitly confirmed by the user, as larger result sets can overwhelm the context window.

Once installed, you can use the Azure TableStore server through Cline. Here are some examples:

  1. Querying a table:
Query the Users table where PartitionKey is 'ACTIVE'

Cline will use the query_table tool with:

{
  "tableName": "Users",
  "filter": "PartitionKey eq 'ACTIVE'",
  "limit": 5  // Optional: Defaults to 5 items. WARNING: Do not increase without user confirmation
}

The response will include:

  • Total number of items that match the query (without limit)
  • Limited subset of items (default 5) for safe LLM processing
  • Applied limit value

For example:

{
  "totalItems": 25,
  "limit": 5,
  "items": [
    // First 5 matching items
  ]
}

This design allows the LLM to understand the full scope of the data while working with a manageable subset. The default limit of 5 items protects against overwhelming the LLM's context window - this limit should only be increased when explicitly confirmed by the user.

  1. Getting table schema:
Show me the schema for the Orders table

Cline will use the get_table_schema tool with:

{
  "tableName": "Orders"
}
  1. Listing tables:
List all tables in the storage account

Cline will use the list_tables tool with:

{}

Project Structure

  • src/index.ts: Main server implementation with Azure Table Storage interaction logic
  • build/: Compiled JavaScript output
  • package.json: Project dependencies and scripts

Dependencies

  • @azure/data-tables: Azure Table Storage client library
  • @modelcontextprotocol/sdk: MCP server implementation toolkit

License

This project is licensed under the MIT License - see the LICENSE file for details. This means you can use, modify, distribute, and sublicense the code freely, provided you include the original copyright notice and license terms.

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client