
Nife
com.nifetencyPublished by nifetency.comOfficial publisherv1.2.0Updated Nov 7, 2026
Manage Nife.io cloud apps, sites, secrets and Git integrations from MCP clients.
Overview
Connects an assistant to the Nife.io GraphQL API so it can list, create and manage cloud apps, sites, deployments, secrets and Git integrations.
- What you can do
- List and inspect Nife.io resources such as applications, sites and deployments
- Create, update and delete resources through GraphQL mutations
- Run custom GraphQL queries and introspect the schema
- Generate MCP tools dynamically from the discovered schema
- When to use it
- Useful when you host apps or sites on Nife.io and want an assistant to check deployment status, create or change applications, or run ad-hoc GraphQL queries against your account without leaving the chat.
- Requirements
- A Nife.io account and an access token (obtained via the nifectl CLI) supplied as the NIFE_ACCESS_TOKEN environment variable; network access to the Nife.io GraphQL API. The hosted connector is reached over OAuth at a remote endpoint; local use needs Python or Node.js depending on the install method.
Installation
In SourceWeft
- Open Nife in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.nifetency%2Fnife-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"nife": {
"type": "http",
"url": "https://mcp.on.nifetency.com/mcp"
}
}
}README
Nife.io MCP Server
[Python] [License: MIT] [Downloads] [Code style: black]
A Model Context Protocol (MCP) server that interfaces with the Nife.io GraphQL API
Overview
Nife MCP Server provides a standardized interface to interact with Nife.io's GraphQL API through the Model Context Protocol, enabling seamless integration with Claude Desktop and other MCP-compatible applications.
Key Features
- Intelligent Schema Discovery - Automatically discovers and adapts to the GraphQL schema
- Dynamic Tool Generation - Creates MCP tools on-the-fly from schema
- Zero Configuration - Works out of the box with minimal setup
- Secure Authentication - Bearer token support with flexible configuration
- Multiple Install Methods - PyPI, NPM, or GitHub
- Cross-Platform - Works on macOS, Linux, and Windows
- Production Ready - Comprehensive error handling and logging
Installation
Option 1: PyPI (Recommended for Python users)
Option 2: NPM (Best for Claude Desktop)
Option 3: From Source
Quick Start
1. Get Your Access Token
2. Configure Claude Desktop
You can use the Nife MCP Server in three ways depending on your setup.
1. Recommended: Using NPX (No Installation Required)
This is the easiest way to get started.
2. Using Python (Installed via pip)
If you installed the package via pip:
Use this configuration:
3. Local Development (Source Code)
If you're running from source:
Replace the PYTHONPATH with your local project path.
Environment Variables
Variable Description
NIFE_ACCESS_TOKEN Your API access token from Nife
3. Restart Claude Desktop
Your Nife.io integration is now active! 🎉
📚 Documentation
- Quick Start - Get started in 5 minutes
- Hosted connector (URL-based) - Deploy the remote server and connect by URL
- API Documentation - Complete API reference
- Release Guide - For contributors and maintainers
- Contributing - How to contribute
Usage
Starting the Server
The server speaks MCP over stdin/stdout, so it is normally launched by your MCP client (e.g. Claude Desktop) rather than run by hand. It does not listen on a network port.
To run the hosted HTTP connector instead, install the http extra (pip install "nife-mcp-server[http]") and run nife-mcp-http. It listens on PORT (default 8000); see HOSTED.md.
Environment Variables
NIFE_ACCESS_TOKEN- Your Nife.io access token
The GraphQL endpoint is fixed to https://api.nife.io/graphql. The hosted connector has its own settings, listed in HOSTED.md.
Example Usage with Claude
Once configured, you can ask Claude:
Architecture
Core Components
- Schema Manager - Intelligent GraphQL schema introspection
- Tool Generator - Dynamic MCP tool creation
- Query Builder - Smart query construction
- Authentication - Secure token management
API Endpoints
MCP Endpoints
GraphQL Integration
The server provides full access to Nife.io's GraphQL API:
- Query all resources (apps, deployments, etc.)
- Execute mutations (create, update, delete)
- Custom query execution
- Schema introspection
Development
Setup Development Environment
Project Structure
Running Tests
Contributing
We love contributions! Please see our Contributing Guide for details.
Ways to Contribute
- Report bugs
- Suggest features
- Improve documentation
- Submit pull requests
Development Process
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests
- Submit a pull request
Stats
[GitHub stars] [GitHub forks] [GitHub issues] [GitHub pull requests]
License
This project is licensed under the MIT License - see the LICENSE file for details.
Acknowledgments
- Built for the Model Context Protocol
- Powered by Nife.io
- Designed for Claude Desktop
Support
- Email: [email protected]
- Issues: GitHub Issues
- Discussions: GitHub Discussions
- Documentation: Full Docs
Roadmap
- WebSocket support for real-time updates
- GraphQL subscriptions
- Enhanced caching layer
- Query batching
- Metrics and monitoring
- Docker Compose examples
- Kubernetes manifests
Star History
If you find this project useful, please consider giving it a star!
Made by the Nife.io team
Source: README.md at commit 1f473b9
Tools
0Version history
1- v1.2.0LatestNov 7, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts