dylog

io.github.imjakezimmer32Published by GitHub account imjakezimmer32v1.0.2Updated Oct 24, 2026

Notes, files, GitHub, and Drive through one MCP connection.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

A remote MCP endpoint that gives an assistant one connection to your notes, files, GitHub and Google Drive.

What you can do
Access notes through the connection, so the assistant can work with your written material alongside other sources. Reach files and Google Drive content, letting the assistant pull in stored documents and data. Work with GitHub through the same connection, bringing repositories and related items into the assistant's reach. All of this is exposed as a single MCP connection rather than separate integrations.
When to use it
Useful when you want an assistant to draw on your notes, files, Drive content and GitHub together in one session, instead of wiring up separate servers for each source.
Requirements
A remote MCP connection to the dylog.app endpoint over streamable HTTP. A bearer token is required, sent in the Authorization header; the token is minted on the provider's Me page and shown only once.
Before you install
The connection is authenticated with a bearer token that is displayed only once, so store it safely; anyone holding it can likely reach the connected notes, files, Drive and GitHub data. The server reaches third-party services (GitHub, Google Drive), so content from those accounts passes through the provider. No tool list is published, so what the assistant can read or change is not documented here.

Installation

In SourceWeft

  1. Open dylog in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.github.imjakezimmer32%2Fdylog/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": {
    "dylog": {
      "type": "http",
      "url": "https://dylog.app/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.