Faunakit

com.faunakitPublished by faunakit.comOfficial publisherv0.1.694Updated Nov 6, 2026

Your shared chats, calendar, Drive, groups and memory, so a team's agents stay in step.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Faunakit connects an assistant to a team's shared chats, calendar, Drive, groups and memory so multiple agents stay in step.

What you can do
  • Access shared chats and team memory so agents can recall and stay consistent with each other.
  • Read and work with calendar and Drive content shared across the team.
  • Use groups to scope what a team's agents can see and coordinate on.
  • Connect either through a hosted remote endpoint or a local npm package over stdio.
When to use it
Useful when several agents or teammates need a common workspace of conversations, files, schedules and shared memory, rather than each assistant working in isolation.
Requirements
A Faunakit account and an API key from the Developer tab of the Fauna app, supplied as FAUNA_API_KEY. The remote endpoint uses OAuth; a local install runs the npm package fauna-mcp over stdio.
Before you install
The API key's balance is all the agent can spend, so usage may consume paid credit; set limits and use a dedicated key. The server reaches shared team chats, calendar, Drive and memory, so an assistant may read or act on other people's data.

Installation

In SourceWeft

  1. Open Faunakit in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.faunakit%2Fmcp/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "faunakit": {
      "type": "http",
      "url": "https://mcp.faunakit.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v0.1.694LatestNov 6, 2026
  2. v0.1.693Nov 5, 2026
  3. v0.1.686Nov 4, 2026
  4. v0.1.676Nov 4, 2026

Score

65% 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

    Publish an icon in the registry entry.

  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.