iknow

dev.iknowPublished by iknow.devOfficial publisherv1.0.0Updated Oct 26, 2026

Knowledge base MCP for AI agents on iknow.dev. Search, read, and maintain via OAuth.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Remote knowledge base server for iknow.dev that lets an assistant search, read and maintain knowledge base content through OAuth.

What you can do
  • Search knowledge base content on iknow.dev
  • Read entries and documents from the knowledge base
  • Maintain and update knowledge base content
  • All access is authenticated through OAuth
When to use it
Useful when an assistant should draw on an iknow.dev knowledge base while answering, or keep that knowledge base up to date as part of a workflow. It fits teams already using iknow.dev rather than general web research.
Requirements
A remote MCP endpoint at iknow.dev over streamable HTTP; no local package or runtime is needed. An iknow.dev account with OAuth authorization is required. No environment variables or headers are declared.
Before you install
The server can maintain knowledge base content, so an assistant may change or delete existing entries; review write actions before granting broad access. Access is tied to your iknow.dev account through OAuth, and content you read or write passes through that service.

Installation

In SourceWeft

  1. Open iknow 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/dev.iknow%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": {
    "iknow": {
      "type": "http",
      "url": "https://iknow.dev/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

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

    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.