Hello MCP 62e940b5

MCP开发工具

提供方 ShanmugaSivapragasam

开发工具 stdio · 本地进程 无需鉴权 社区 / 第三方 Claude
查看接入方式

一个基于Spring Boot的MCP服务器,提供与Claude、Perplexity、ChatGPT等AI客户端的集成工具,适合企业级部署。

一句话选型结论

按资料字段整理

Hello MCP 62e940b5 属于开发工具类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 1 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量1暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

Shell本地部署AI集成企业级服务SpringBoot应用MCP协议云原生

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
docker run -d \

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Docker,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 1 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 1 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Hello MCP 62e940b5当前 1 stdio · 本地进程 本地部署 有 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方ShanmugaSivapragasam上游标注的维护方 ShanmugaSivapragasam
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Docker本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

17.7 KB
来自项目仓库与上游目录的原文,未做删改

Hello MCP Server

A production-ready Spring Boot MCP (Model Context Protocol) server that provides AI tools for integration with Claude, Perplexity, ChatGPT, and other AI clients. Built with Spring AI MCP framework for enterprise-grade deployment.

Overview

This MCP server exposes AI tools through the Model Context Protocol, enabling seamless integration with various AI platforms. The server provides a hello-tool that demonstrates the MCP architecture and can be extended with custom business logic.

Key Features

  • ✅ Production Ready: Built with Spring Boot 3.5.7 and Java 21
  • ✅ MCP Protocol Compliant: Uses Spring AI MCP Server WebMVC
  • ✅ Enterprise Grade: Comprehensive logging, monitoring, and security
  • ✅ Scalable Architecture: Supports horizontal scaling and load balancing
  • ✅ Multi-AI Platform Support: Compatible with Claude, ChatGPT, Perplexity
  • ✅ Cloud Native: Docker and Kubernetes ready

Technical Specifications

  • Framework: Spring Boot 3.5.7
  • Java Version: 21
  • Build Tool: Gradle 8.x
  • Protocol: MCP (Model Context Protocol)
  • Architecture: Microservice/Standalone
  • Deployment: JAR, Docker, Kubernetes

🚀 Quick Start (30 seconds)```bash

Clone and start the server

git clone https://github.com/your-org/hello-mcp.git
cd hello-mcp
./start.sh


The server will be running at `http://localhost:8080` with MCP tools ready for AI integration!

## Available Tools

### hello-tool
- **Description**: Returns a greeting message from the MCP server
- **Usage**: Demonstrates MCP tool functionality
- **Response**: `"Hello from MCP server!"`
- **Spring Boot**: 3.5.7
- **Spring AI**: 1.1.0-M4 (with MCP server support)
- **Gradle**: 8.14.3
- **Build Tool**: Gradle Wrapper

## Features

- MCP server implementation with Spring AI
- Simple greeting tool (`hello-tool`)
- Configurable MCP server settings
- RESTful web endpoints
- Comprehensive logging

## Project Structure```
src/main/java/com/shan/hello_mcp/
├── HelloMcpApplication.java    # Main Spring Boot application
└── HelloTools.java             # MCP tools implementation

Getting Started

Prerequisites

  • Java 25 or higher
  • Git

Installation and Setup

  1. Clone the repository:bash git clone <repository-url> cd hello-mcp

  2. Build the project:bash ./gradlew build

  3. Run the application:bash ./gradlew bootRun

The application will start on the default port (8080) and the MCP server will be available for client connections.

Configuration

The MCP server is configured in application.properties:```properties
spring.application.name=hello-mcp
spring.ai.mcp.server.name=HelloMCPServer
spring.ai.mcp.server.description=A simple MCP server application
spring.ai.mcp.server.version=1.0.0
spring.ai.mcp.server.author=Shan
spring.ai.mcp.server.protocol=streamable
spring.ai.mcp.server.stdio=false
spring.ai.mcp.server.type=sync


## Available Tools

### hello-tool

- **Name**: `hello-tool`
- **Description**: A tool that returns a hello message from the MCP server
- **Response**: Returns "Hello from MCP server!" message

## Usage Example

When connected to an MCP client, you can call the `hello-tool` to receive a greeting message. The tool will log the call and return the greeting response.

## Development

### Running Tests```bash
./gradlew test

Building for Production```bash

./gradlew bootJar


The executable JAR will be created in `build/libs/`.

## Dependencies

Key dependencies include:
- `spring-boot-starter-web`: Web framework support
- `spring-ai-starter-mcp-server-webmvc`: MCP server implementation
- `spring-boot-starter-test`: Testing framework

## Author

Shan

## Version

0.0.1-SNAPSHOT

## Quick Start

### Prerequisites

- Java 21 or higher
- Gradle 8.x
- Git
- Docker (optional)
- Kubernetes (for production deployment)

### Development Setup

1. **Clone the repository**```bash
   git clone https://github.com/your-org/hello-mcp.git
   cd hello-mcp
   ```

2. **Build the application**```bash
   ./gradlew build
   ```

3. **Run locally**```bash
   ./gradlew bootRun
   ```

4. **Verify the server**```bash
   curl http://localhost:8080/actuator/health
   ```

## Production Deployment Guide

### Option 1: Traditional JAR Deployment

#### 1. Build Production JAR```bash
./gradlew clean build -Pprofile=prod

2. Server Setup (Ubuntu/RHEL)```bash

Create application user

sudo useradd -r -s /bin/false mcp-server

Create directories

sudo mkdir -p /opt/mcp-server/{bin,config,logs}
sudo chown -R mcp-server:mcp-server /opt/mcp-server

Copy JAR

sudo cp build/libs/hello-mcp-0.0.1-SNAPSHOT.jar /opt/mcp-server/bin/


#### 3. Production Configuration
Create `/opt/mcp-server/config/application-prod.properties`:```properties
# Server Configuration
server.port=8080
server.servlet.context-path=/mcp
server.shutdown=graceful
spring.lifecycle.timeout-per-shutdown-phase=30s

# MCP Server Configuration
spring.application.name=hello-mcp
spring.ai.mcp.server.name=HelloMCPServer-Prod
spring.ai.mcp.server.description=Production MCP server
spring.ai.mcp.server.version=1.0.0
spring.ai.mcp.server.author=Enterprise Team

# Protocol Configuration
spring.ai.mcp.server.protocol=streamable
spring.ai.mcp.server.stdio=false
spring.ai.mcp.server.type=sync

# Logging Configuration
logging.level.com.shan.hello_mcp=INFO
logging.level.org.springframework.ai.mcp=DEBUG
logging.pattern.file=%d{yyyy-MM-dd HH:mm:ss} [%thread] %-5level %logger{36} - %msg%n
logging.file.name=/opt/mcp-server/logs/application.log
logging.logback.rollingpolicy.max-file-size=100MB
logging.logback.rollingpolicy.total-size-cap=1GB

# Actuator (Monitoring)
management.endpoints.web.exposure.include=health,info,metrics,prometheus
management.endpoint.health.show-details=when-authorized
management.metrics.export.prometheus.enabled=true

# Security (if enabled)
management.endpoints.web.base-path=/actuator
management.server.port=9090

4. SystemD Service

Create /etc/systemd/system/mcp-server.service:```ini
[Unit]
Description=Hello MCP Server
After=network.target

[Service]
Type=simple
User=mcp-server
Group=mcp-server
WorkingDirectory=/opt/mcp-server
ExecStart=/usr/bin/java \
-Xms512m -Xmx2g \
-XX:+UseG1GC \
-XX:MaxGCPauseMillis=200 \
-Dspring.profiles.active=prod \
-Dspring.config.location=/opt/mcp-server/config/ \
-jar /opt/mcp-server/bin/hello-mcp-0.0.1-SNAPSHOT.jar
ExecStop=/bin/kill -TERM $MAINPID
Restart=always
RestartSec=30
StandardOutput=journal
StandardError=journal

[Install]
WantedBy=multi-user.target


#### 5. Start Service```bash
sudo systemctl daemon-reload
sudo systemctl enable mcp-server
sudo systemctl start mcp-server
sudo systemctl status mcp-server

Option 2: Docker Deployment

1. Create Dockerfile```dockerfile

FROM openjdk:25-jdk-slim

Create app user

RUN groupadd -r mcpuser && useradd -r -g mcpuser mcpuser

Set working directory

WORKDIR /app

Copy JAR

COPY build/libs/hello-mcp-*.jar app.jar

Create logs directory

RUN mkdir -p /app/logs && chown -R mcpuser:mcpuser /app

Switch to non-root user

USER mcpuser

Health check

HEALTHCHECK --interval=30s --timeout=10s --start-period=60s --retries=3 \
CMD curl -f http://localhost:8080/actuator/health || exit 1

Expose ports

EXPOSE 8080 9090

JVM options for containers

ENV JAVA_OPTS="-Xms512m -Xmx1g -XX:+UseContainerSupport -XX:MaxRAMPercentage=75.0"

Run application

ENTRYPOINT ["sh", "-c", "java $JAVA_OPTS -jar app.jar"]


#### 2. Build and Run```bash
# Build image
docker build -t hello-mcp:latest .

# Run container
docker run -d \
  --name mcp-server \
  -p 8080:8080 \
  -p 9090:9090 \
  -e SPRING_PROFILES_ACTIVE=prod \
  -v /opt/mcp-server/logs:/app/logs \
  --restart unless-stopped \
  hello-mcp:latest

Option 3: Kubernetes Deployment

1. Create Kubernetes Manifests

namespace.yaml```yaml
apiVersion: v1
kind: Namespace
metadata:
name: mcp-server
labels:
name: mcp-server


**configmap.yaml**```yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: mcp-server-config
  namespace: mcp-server
data:
  application-prod.properties: |
    server.port=8080
    spring.profiles.active=prod
    spring.ai.mcp.server.name=HelloMCPServer-K8s
    logging.level.com.shan.hello_mcp=INFO
    management.endpoints.web.exposure.include=health,info,metrics,prometheus

deployment.yaml```yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: mcp-server
namespace: mcp-server
labels:
app: mcp-server
spec:
replicas: 3
selector:
matchLabels:
app: mcp-server
template:
metadata:
labels:
app: mcp-server
spec:
containers:
- name: mcp-server
image: hello-mcp:latest
ports:
- containerPort: 8080
- containerPort: 9090
env:
- name: SPRING_PROFILES_ACTIVE
value: "prod"
- name: JAVA_OPTS
value: "-Xms512m -Xmx1g -XX:+UseContainerSupport"
volumeMounts:
- name: config-volume
mountPath: /app/config
livenessProbe:
httpGet:
path: /actuator/health
port: 9090
initialDelaySeconds: 60
periodSeconds: 30
readinessProbe:
httpGet:
path: /actuator/health/readiness
port: 9090
initialDelaySeconds: 30
periodSeconds: 10
resources:
requests:
memory: "512Mi"
cpu: "250m"
limits:
memory: "2Gi"
cpu: "1000m"
volumes:
- name: config-volume
configMap:
name: mcp-server-config


**service.yaml**```yaml
apiVersion: v1
kind: Service
metadata:
  name: mcp-server-service
  namespace: mcp-server
  labels:
    app: mcp-server
spec:
  selector:
    app: mcp-server
  ports:
  - name: http
    port: 8080
    targetPort: 8080
  - name: management
    port: 9090
    targetPort: 9090
  type: ClusterIP

ingress.yaml```yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: mcp-server-ingress
namespace: mcp-server
annotations:
nginx.ingress.kubernetes.io/rewrite-target: /
cert-manager.io/cluster-issuer: "letsencrypt-prod"
spec:
tls:
- hosts:
- mcp.yourdomain.com
secretName: mcp-server-tls
rules:
- host: mcp.yourdomain.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: mcp-server-service
port:
number: 8080


#### 2. Deploy to Kubernetes```bash
# Apply manifests
kubectl apply -f k8s/

# Verify deployment
kubectl get pods -n mcp-server
kubectl get services -n mcp-server
kubectl logs -f deployment/mcp-server -n mcp-server

Load Balancer & Reverse Proxy Setup

Nginx Configuration```nginx

upstream mcp_backend {
server 10.0.1.10:8080 max_fails=3 fail_timeout=30s;
server 10.0.1.11:8080 max_fails=3 fail_timeout=30s;
server 10.0.1.12:8080 max_fails=3 fail_timeout=30s;
}

server {
listen 80;
listen 443 ssl http2;
server_name mcp.yourdomain.com;

# SSL Configuration
ssl_certificate /etc/ssl/certs/mcp.yourdomain.com.crt;
ssl_certificate_key /etc/ssl/private/mcp.yourdomain.com.key;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-RSA-AES256-GCM-SHA512:DHE-RSA-AES256-GCM-SHA512;

# Security Headers
add_header X-Frame-Options DENY;
add_header X-Content-Type-Options nosniff;
add_header X-XSS-Protection "1; mode=block";
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;

# Rate Limiting
limit_req_zone $binary_remote_addr zone=mcp_limit:10m rate=10r/s;
limit_req zone=mcp_limit burst=20 nodelay;

location / {
    proxy_pass http://mcp_backend;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

    proxy_connect_timeout 30s;
    proxy_send_timeout 30s;
    proxy_read_timeout 30s;

    proxy_buffer_size 4k;
    proxy_buffers 8 4k;
    proxy_busy_buffers_size 8k;
}

location /actuator {
    deny all;
    return 403;
}

}


## AI Platform Integration

### Claude Integration```python
import anthropic
import requests

# MCP Server connection
MCP_SERVER_URL = "https://mcp.yourdomain.com"

def call_mcp_tool(tool_name, **kwargs):
    response = requests.post(
        f"{MCP_SERVER_URL}/mcp/tools/{tool_name}",
        json=kwargs,
        headers={"Content-Type": "application/json"}
    )
    return response.json()

# Use with Claude
client = anthropic.Anthropic(api_key="your-api-key")

# Call MCP tool
greeting = call_mcp_tool("hello-tool")
print(f"MCP Response: {greeting}")

ChatGPT Integration```javascript

const axios = require('axios');

const MCP_SERVER_URL = 'https://mcp.yourdomain.com';

async function callMcpTool(toolName, params = {}) {
try {
const response = await axios.post(
${MCP_SERVER_URL}/mcp/tools/${toolName},
params,
{
headers: { 'Content-Type': 'application/json' }
}
);
return response.data;
} catch (error) {
console.error('MCP Tool Error:', error);
throw error;
}
}

// Example usage
async function main() {
const greeting = await callMcpTool('hello-tool');
console.log('MCP Response:', greeting);
}


### Perplexity Integration```python
import requests
from typing import Dict, Any

class McpClient:
    def __init__(self, base_url: str):
        self.base_url = base_url.rstrip('/')

    def call_tool(self, tool_name: str, **kwargs) -> Dict[str, Any]:
        response = requests.post(
            f"{self.base_url}/mcp/tools/{tool_name}",
            json=kwargs,
            timeout=30
        )
        response.raise_for_status()
        return response.json()

# Initialize MCP client
mcp = McpClient("https://mcp.yourdomain.com")

# Use with Perplexity workflows
def enhanced_search_with_mcp():
    # Call MCP tool first
    greeting = mcp.call_tool("hello-tool")

    # Then proceed with Perplexity search
    return greeting

Monitoring & Observability

Prometheus Metrics

Access metrics at: http://your-server:9090/actuator/prometheus

Key metrics to monitor:
- jvm_memory_used_bytes
- http_server_requests_seconds
- mcp_tool_calls_total
- application_ready_time_seconds

Grafana Dashboard

Import the provided Grafana dashboard JSON for comprehensive monitoring.

Log Analysis```bash

View real-time logs

sudo journalctl -u mcp-server -f

Search for specific patterns

sudo journalctl -u mcp-server | grep "ERROR|WARN"

Export logs for analysis

sudo journalctl -u mcp-server --since="1 hour ago" > /tmp/mcp-logs.txt


## Security Considerations

### Production Security Checklist

- [ ] **Network Security**
  - Firewall configured (only ports 80, 443, 22 open)
  - VPN/VPC for internal communication
  - Load balancer with SSL termination

- [ ] **Application Security**
  - Spring Security enabled
  - Rate limiting implemented
  - Input validation on all endpoints
  - CORS properly configured

- [ ] **Infrastructure Security**
  - Regular security updates
  - Non-root user execution
  - Secrets management (HashiCorp Vault/K8s Secrets)
  - Container scanning for vulnerabilities

- [ ] **Monitoring & Alerting**
  - Real-time error alerting
  - Performance monitoring
  - Security event logging
  - Audit trail maintenance

### Environment Variables```bash
# Required for production
export SPRING_PROFILES_ACTIVE=prod
export MCP_SERVER_SECRET_KEY=your-secret-key
export DATABASE_URL=your-database-url
export MONITORING_API_KEY=your-monitoring-key

Troubleshooting

Common Issues

  1. Port Already in Usebash sudo lsof -i :8080 sudo kill -9 <PID>

  2. Memory Issuesbash # Increase JVM heap size export JAVA_OPTS="-Xms1g -Xmx4g"

  3. MCP Connection Issuesbash # Check MCP endpoint curl -v http://localhost:8080/mcp/tools

  4. SSL Certificate Issuesbash # Verify certificate openssl x509 -in /path/to/cert.pem -text -noout

Performance Tuning

JVM Tuning for Production```bash

JAVA_OPTS="
-Xms2g -Xmx4g
-XX:+UseG1GC
-XX:MaxGCPauseMillis=200
-XX:+UseStringDeduplication
-XX:+OptimizeStringConcat
-XX:+UseCompressedOops
-Djava.security.egd=file:/dev/./urandom
"


#### Database Connection Pool```properties
# HikariCP Configuration
spring.datasource.hikari.minimum-idle=10
spring.datasource.hikari.maximum-pool-size=50
spring.datasource.hikari.idle-timeout=300000
spring.datasource.hikari.max-lifetime=600000
spring.datasource.hikari.connection-timeout=20000

Scaling & High Availability

Horizontal Scaling

  • Deploy multiple instances behind a load balancer
  • Use session-less design (stateless)
  • Implement circuit breakers for resilience

Vertical Scaling

  • Monitor CPU/memory usage
  • Adjust JVM heap sizes accordingly
  • Use profiling tools for optimization

Database Scaling

  • Read replicas for read-heavy workloads
  • Connection pooling optimization
  • Query performance tuning

Support & Maintenance

Regular Maintenance Tasks

  1. Weekly
    - Review application logs
    - Check system metrics
    - Update dependencies (security patches)

  2. Monthly
    - Performance review
    - Capacity planning
    - Security audit

  3. Quarterly
    - Disaster recovery testing
    - Architecture review
    - Technology stack updates

Getting Help

  • Documentation: Check the Wiki
  • Issues: Report bugs on GitHub Issues
  • Community: Join our Discord
  • Commercial Support: Contact enterprise@yourcompany.com

License

This project is licensed under the MIT License - see the LICENSE file for details.


Enterprise Support Available - Contact us for production support, custom features, and SLA guarantees.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Hello MCP 62e940b5 怎么安装?

在客户端按下面的安装命令接入:docker run -d \。装完在客户端配置里引用同一个包或端点。

Hello MCP 62e940b5 怎么在 Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Hello MCP 62e940b5 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Hello MCP 62e940b5 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Hello MCP 62e940b5 支持哪些客户端?

资料标注支持 Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Hello MCP 62e940b5 能提供哪些能力?

资料显示约 1 个工具;能力标签包括 云原生、Shell、Claude。具体工具清单以官方文档为准。

Hello MCP 62e940b5 需要什么运行环境?

运行时为 Docker;属于本地进程,需要在本机装好运行环境。

Hello MCP 62e940b5 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。