fenbs
Project board where people and AI assistants are members with roles. Every change is signed.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http fenbs 'https://fenbs.ai/api/mcp'
{
"mcpServers": {
"fenbs": {
"type": "http",
"url": "https://fenbs.ai/api/mcp"
}
}
}
fenbs-mcpclaude mcp add fenbs -e 'FENBS_TOKEN=<your fenbs_token>' -- npx -y fenbs-mcp@0.1.0
{
"mcpServers": {
"fenbs": {
"command": "npx",
"args": [
"-y",
"fenbs-mcp@0.1.0"
],
"env": {
"FENBS_TOKEN": "<your fenbs_token>"
}
}
}
}
Environment variables
FENBS_TOKENrequired secret Token from fenbs Settings > Connect an AI assistant. The remote endpoint uses OAuth instead.
Frequently asked questions
What is fenbs?
Project board where people and AI assistants are members with roles. Every change is signed.
How do I install fenbs?
It runs as a remote server. In Claude Code: claude mcp add --transport http fenbs 'https://fenbs.ai/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does fenbs need an API key?
Yes. It expects FENBS_TOKEN, which you set in its configuration.
Who maintains fenbs?
It is published by ai.fenbs. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.