Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ A Model Context Protocol (MCP) server that provides tools for interacting with C
- **JWE Authentication**: Optional JWE-based authentication with encryption for secure database access
- **TLS Support**: Full TLS encryption support for both ClickHouse® connections and MCP server endpoints
- **Comprehensive Tools**: Built-in tools for listing tables, describing schemas, and executing queries
- **Dynamic Tools**: Automatically generate MCP tools from ClickHouse® views (see [Dynamic Tools Documentation](docs/dynamic_tools.md))
- **Dynamic Tools**: Automatically generate MCP tools from ClickHouse® views and tables (see [Tools Documentation](docs/tools.md))
- **Resource Templates**: Dynamic resource discovery for database schemas and table information
- **Query Prompts**: AI-assisted query building and optimization prompts
- **Configuration Management**: Flexible configuration via files, environment variables, or CLI flags
Expand Down Expand Up @@ -203,7 +203,7 @@ logging:
level: "info"
```

> **Note**: For detailed information about dynamic tools configuration, see the [Dynamic Tools Documentation](docs/dynamic_tools.md).
> **Note**: For detailed information about dynamic tools configuration, see the [Tools Documentation](docs/tools.md).

Use the configuration file:

Expand Down Expand Up @@ -247,7 +247,7 @@ View `COMMENT` supports either:
- A plain string description.
- A strict JSON object with top-level `title`, `description`, and `annotations`.

See [Dynamic Tools Documentation](docs/dynamic_tools.md) for examples and supported metadata.
See [Tools Documentation](docs/tools.md) for examples and supported metadata.

## Available Resources

Expand Down
300 changes: 0 additions & 300 deletions docs/dynamic_tools.md

This file was deleted.

14 changes: 7 additions & 7 deletions docs/howto_integrate.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ To integrate Altinity MCP with Claude.ai:

![Claude Web Integration Step 2](screenshots/claude_web_connectors_1.jpg)

* Enter a name for your connector (e.g., `altinity-mcp-jwe`) and the server URL, which should include the JWE token. For example: `https://host/token/http`.
* Enter a name for your connector (e.g., `altinity-mcp-jwe`) and the server URL, which should include the JWE token. For example: `https://host/token`.

![Claude Web Integration Step 3](screenshots/claude_web_connectors_2.jpg)

Expand Down Expand Up @@ -148,7 +148,7 @@ To integrate Altinity MCP with Claude Desktop:
"mcpServers": {
"altinity-mcp": {
"command": "npx",
"args": ["-y", "mcp-remote", "http{s}://your-mcp-host:port/generated_jwe_token/http"]
"args": ["-y", "mcp-remote", "http{s}://your-mcp-host:port/generated_jwe_token"]
}
}
}
Expand All @@ -162,10 +162,10 @@ Download and install Claude Code https://www.anthropic.com/claude-code
To integrate Altinity MCP with Claude Code, you can use the `claude mcp add` command for HTTP transport:

```bash
claude mcp add --transport http altinity-mcp https://your-mcp-host:port/generated_jwe_token/http
claude mcp add --transport http altinity-mcp https://your-mcp-host:port/generated_jwe_token
```

Replace `https://your-mcp-host:port/generated_jwe_token/http` with the actual URL of your Altinity MCP server, including the JWE token and `/http` suffix.
Replace `https://your-mcp-host:port/generated_jwe_token` with the actual URL of your Altinity MCP server, including the JWE token.

This command will configure Claude Code to use your Altinity MCP server as a tool provider.

Expand All @@ -180,7 +180,7 @@ Pasting the following configuration into your Cursor `~/.cursor/mcp.json` file i
{
"mcpServers": {
"altinity-mcp": {
"url": "https://your-mcp-server-url:port/default/http",
"url": "https://your-mcp-server-url:port/default",
"headers": {
"Authorization": "Bearer your-jwe-token"
}
Expand All @@ -200,7 +200,7 @@ Add this to your Windsurf MCP config file. See [Windsurf MCP docs](https://docs.
{
"mcpServers": {
"context7": {
"serverUrl": "https://your-mcp-server-url:port/default/http",
"serverUrl": "https://your-mcp-server-url:port/default",
"headers": {
"Authorization": "Bearer your-jwe-token"
}
Expand All @@ -215,7 +215,7 @@ Add this to your Windsurf MCP config file. See [Windsurf MCP docs](https://docs.
If you encounter issues during integration:

1. Verify your Altinity MCP server is running and accessible
2. Ensure your JWE token is valid and not (use `curl -vvv https://your-mcp-host/your_jwe_token/http`)
2. Ensure your JWE token is valid (use `curl -vvv https://your-mcp-host/your_jwe_token`)
3. Check that the server configuration matches the integration settings
4. Confirm network connectivity between the AI tool and your Altinity MCP server
5. Review server logs for authentication or connection errors
Expand Down
Loading