Higgfield MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Higgfield MCPcall the Stripe API with my stored key to list recent charges"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Higgfield MCP
A production-ready MCP (Model Context Protocol) server for API key management, generation tracking, and external API calling with Twynity integration.
Features
✅ JWT Authentication - Secure bearer token verification with account-service JWKS
✅ Persona-Based Access - Strict
(user_id, persona_id)pairing for multi-tenancy✅ Encrypted Storage - Fernet encryption for sensitive credentials
✅ MCP Tools Integration - Tools accessible to both LLMs and MCP Apps UI
✅ External API Calls - Call third-party services using stored credentials
✅ File Operations - Local file system access for owners
✅ Usage Tracking - Fire-and-forget usage reporting
✅ License Management - Automatic license validation with grace period
✅ React UI - Built-in MCP Apps UI for tool visualization
✅ Comprehensive Testing - Unit and integration tests
✅ Docker Support - Multi-stage Docker builds
Related MCP server: AgentPay MCP Server
Quick Start
Prerequisites
Python 3.12+
npm (for UI development)
Docker (optional, but recommended)
Installation
Clone the repository:
git clone <your-repo-url>
cd higgfield-mcpInstall dependencies:
uv syncConfigure environment variables:
cp .env.example .envEdit .env with your settings (see Configuration section).
Run the server:
uv run python -m uvicorn app.main:app --reloadAccess the API docs:
http://localhost:8000/docsConfiguration
Required environment variables:
# Service Identity
SERVICE_ID=higgfield-mcp
APP_TITLE=Higgfield MCP
APP_VERSION=1.0.0
# Security
ALLOWED_ORIGINS=*
PERSONA_ID_HEADER=Persona-Id
# Account Service (JWT verification)
ACCOUNT_SERVICE_URL=http://account_service:8000
ACCOUNT_SERVICE_JWKS_ENDPOINT=/.well-known/jwks.json
# MongoDB
MONGODB_URI=mongodb://mongo:27017
MONGODB_DB=higgfield
ENCRYPTION_KEY=REPLACE_WITH_32_CHAR_KEY_FOR_FERNET
# Usage Reporting (optional)
USAGE_REPORT_ENDPOINT=http://usage-reporting:8000/api/v1/usageDevelopment
Running Tests
# Run all tests
uv run pytest
# Run specific test file
uv run pytest tests/test_auth.py
# Run with coverage
uv run pytest --cov=app --cov-report=htmlLinting
# Check code style
uv run ruff check app tests
# Fix auto-fixable issues
uv run ruff check --fix app testsBuilding UI
cd app/ui/file_dir
npm install
npm run buildDocker
# Build and run with Docker Compose
docker-compose up --build
# Build Docker image
docker build -t higgfield-mcp .Architecture
Core Components
app/auth.py: JWT verification and identity resolutionapp/config.py: Service configuration and settingsapp/connection_store.py: Encrypted MongoDB storageapp/license.py: License managementapp/usage.py: Usage tracking middlewareapp/twynity.py: Twynity-specific HTTP routes
MCP Tools
app/tools/api_call.py: External API callsapp/tools/files.py: File system operationsapp/tools/generational.py: Generation trackingapp/tools/render_content.py: Content rendering
API Endpoints
GET /api/v1/manifest/mcp.json: Public manifest endpointGET /api/v1/schema: Configuration schemaPOST /api/v1/keys: Create API keyGET /api/v1/keys: List API keysPOST /api/v1/generations: Create generationGET /api/v1/generations: List generations
Twynity Integration
Custom HTTP routes with explicit JWT verification
MCP Apps UI support with tool-to-resource linking
Persona-Id header forwarding for authenticated calls
External connections manifest
Security Best Practices
Never disable signature verification - Always use JWT with JWKS
Enforce exact
(user_id, persona_id)pairing - Never fall back to user-only lookupsEncrypt all credentials - Use Fernet encryption before storage
Never log or return secrets - Use safe metadata-only GET responses
Validate Persona-Id from headers - Never accept from untrusted sources
Use timeouts on outbound calls - Prevent hanging requests
License
MIT License - See LICENSE file for details
Contributing
Fork the repository
Create a feature branch:
git checkout -b feature/amazing-featureMake your changes
Run tests:
uv run pytestRun linter:
uv run ruff check app testsSubmit a pull request
Support
For issues and questions, please open an issue on GitHub or contact the development team.
Version History
1.0.0 - Initial release with basic MCP functionality
1.0.1 - Added Twynity integration and comprehensive testing
Changelog
See CHANGELOG.md for version-specific changes.
This server cannot be deployed
Maintenance
Related MCP Connectors
Give your AI hands. Identity, credential vault, and API gateway for autonomous agents.
- FullmaktOAuthai.fullmakt
Credential broker for AI agents: scoped, revocable API access with policy enforcement and audit.
Connect AI agents to 580+ APIs with OAuth or API-key auth. Hosted gateway; API pricing varies.
Verified, pay-per-use API tools for AI agents through one authenticated connection.
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnables secure management of API keys through an encrypted environment file with automatic categorization, search functionality, and backup operations. Provides comprehensive API key organization with value masking, audit trails, and export capabilities for safe credential management.-
- FlicenseNot gradedqualityAmaintenanceProvides a trust and governance layer for AI agents, enabling secure API access, credential vaulting, paid execution with human approval, and automatic call resume.6 npm2-

agentkeys-mcpofficial
AlicenseNot gradedqualityDmaintenanceEnables AI agents to securely manage API credentials and make proxied API calls through AgentKeys, keeping secrets hidden from the agent.10 npmMIT- AlicenseNot gradedqualityBmaintenanceSecure, encrypted API key management for AI coding agents, enabling search, inspection, and use of credentials with scoped permissions and optional zero-knowledge decryption.MIT