Kenva

io.github.kenvaappPublished by GitHub account kenvaappv1.0.0Updated Oct 24, 2026

Personal CRM for Claude. Contacts live as plain-text files in your own Google Drive.

VerifiedStreamable HTTPWeb executableFiles & StorageBusiness & Commerce

Overview

AI-generated overview

Kenva is a personal CRM MCP server that lets an assistant work with your contacts, which are stored as plain-text files in your own Google Drive.

What you can do
  • Work with a personal CRM from the assistant: contacts are kept as plain-text files in your own Google Drive.
  • The listing gives no tool names, so the exact read and write actions are not documented here.
  • Because the data lives in your Drive as plain text, expect the assistant to reach contacts through that storage rather than a separate hosted database.
When to use it
Worth considering if you want an assistant to help manage personal and professional relationships, and you prefer contact records kept as plain text in your own Google Drive instead of a vendor's database.
Requirements
A remote MCP endpoint reached over streamable HTTP; nothing to install locally. The manifest declares no authentication, environment variables or headers, and no Google Drive connection details are documented, so confirm how your Drive is linked before relying on it.
Before you install
The server handles personal contact data and is tied to your Google Drive, so check who can reach the endpoint and what it can read or change in your Drive. No authentication is declared in the manifest, which is worth verifying before connecting. Contact records may be created or modified; review changes.

Installation

In SourceWeft

  1. Open Kenva in the dashboard and add it to a workspace.
  2. 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/io.github.kenvaapp%2Fkenva/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "kenva": {
      "type": "http",
      "url": "https://kenva-crm-mcp-server.kenva.workers.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.