Syntra PMO

io.github.Syntra-TymkoPublished by GitHub account Syntra-Tymkov1.0.0Updated Oct 24, 2026

Project management for your AI assistant: projects, tasks, risks and sprints of a Syntra workspace

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an AI assistant access projects, tasks, risks and sprints in a Syntra workspace.

What you can do
This server exposes project management data from a Syntra workspace to an AI assistant, covering projects, tasks, risks and sprints. It connects over a remote endpoint so the assistant can work with those items in the same workspace context. The input does not list individual tools, so the exact operations available cannot be confirmed.
When to use it
Use it when a team already manages projects in a Syntra workspace and wants the assistant to work with projects, tasks, risks and sprints directly. It adds little if you only need general file or code operations.
Requirements
Network access to the remote endpoint and OAuth authorization; no local package or environment variables are declared.
Before you install
Requires OAuth authorization to a Syntra workspace, which may expose internal project and task data. The input does not say whether data can be changed or deleted, so confirm the granted scopes before authorizing.

Installation

In SourceWeft

  1. Open Syntra PMO 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/io.github.Syntra-Tymko%2Fsyntra/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": {
    "syntra-pmo": {
      "type": "http",
      "url": "https://syntra.tymko.tech/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.0LatestOct 15, 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.