Action Log

app.actionlogPublished by actionlog.appOfficial publisherv1.0.0Updated Nov 8, 2026

Executive status across Jira, Azure DevOps and Basecamp: workstreams, scorecard and actions.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & Analytics

Overview

AI-generated overview

Remote MCP server that gives an assistant executive status across Jira, Azure DevOps and Basecamp: workstreams, scorecard and actions.

What you can do
  • Read executive status spanning Jira, Azure DevOps and Basecamp.
  • Review workstreams and their progress.
  • Consult a scorecard of status metrics.
  • Look up actions and follow-ups.
  • No tool list is published, so exact operations are not documented.
When to use it
Useful when you want an assistant to summarize cross-tool project status for leadership or check workstreams, scorecard and actions without opening each tracker.
Requirements
A remote streamable HTTP endpoint at the provider's site; OAuth authentication is required. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your connected project data in Jira, Azure DevOps and Basecamp, so review the scopes requested. The published material does not say whether any tools write or change data.

Installation

In SourceWeft

  1. Open Action Log 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/app.actionlog%2Faction-log/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": {
    "action-log": {
      "type": "http",
      "url": "https://www.actionlog.app/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.0LatestNov 8, 2026

Score

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

    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.