taskadence-mcp 0.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- taskadence_mcp-0.1.0/.gitignore +29 -0
- taskadence_mcp-0.1.0/LICENSE +202 -0
- taskadence_mcp-0.1.0/NOTICE +2 -0
- taskadence_mcp-0.1.0/PKG-INFO +222 -0
- taskadence_mcp-0.1.0/README.md +181 -0
- taskadence_mcp-0.1.0/pyproject.toml +77 -0
- taskadence_mcp-0.1.0/src/taskadence_mcp/__init__.py +14 -0
- taskadence_mcp-0.1.0/src/taskadence_mcp/__main__.py +3 -0
- taskadence_mcp-0.1.0/src/taskadence_mcp/_version.py +3 -0
- taskadence_mcp-0.1.0/src/taskadence_mcp/cli.py +57 -0
- taskadence_mcp-0.1.0/src/taskadence_mcp/config.py +131 -0
- taskadence_mcp-0.1.0/src/taskadence_mcp/proxy.py +182 -0
- taskadence_mcp-0.1.0/src/taskadence_mcp/py.typed +0 -0
- taskadence_mcp-0.1.0/tests/test_proxy.py +379 -0
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
# Python
|
|
2
|
+
__pycache__/
|
|
3
|
+
*.py[cod]
|
|
4
|
+
*.egg-info/
|
|
5
|
+
.venv/
|
|
6
|
+
venv/
|
|
7
|
+
build/
|
|
8
|
+
dist/
|
|
9
|
+
.pytest_cache/
|
|
10
|
+
.mypy_cache/
|
|
11
|
+
.ruff_cache/
|
|
12
|
+
.coverage
|
|
13
|
+
htmlcov/
|
|
14
|
+
sbom*.json
|
|
15
|
+
|
|
16
|
+
# Secrets: never committed (the CLI's token lives in the OS keyring or ~/.config/taskadence/, never in the repo)
|
|
17
|
+
.env
|
|
18
|
+
.env.*
|
|
19
|
+
*.token
|
|
20
|
+
.streamlit/secrets.toml
|
|
21
|
+
|
|
22
|
+
# OS / editors
|
|
23
|
+
.DS_Store
|
|
24
|
+
.idea/
|
|
25
|
+
.vscode/
|
|
26
|
+
|
|
27
|
+
# Node (packages/mcp-node)
|
|
28
|
+
node_modules/
|
|
29
|
+
*.tgz
|
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
|
@@ -0,0 +1,222 @@
|
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
|
+
Name: taskadence-mcp
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: The TasKadence MCP server for clients that start a local process: a stdio proxy to the remote server (uvx taskadence-mcp).
|
|
5
|
+
Project-URL: Homepage, https://taskadence.com
|
|
6
|
+
Project-URL: Documentation, https://docs.taskadence.com/mcp/connect/
|
|
7
|
+
Project-URL: Source, https://github.com/indrasol/taskadence-python/tree/main/packages/taskadence-mcp
|
|
8
|
+
Project-URL: Issues, https://github.com/indrasol/taskadence-python/issues
|
|
9
|
+
Project-URL: Changelog, https://github.com/indrasol/taskadence-python/blob/main/CHANGELOG.md
|
|
10
|
+
Author: Indrasol
|
|
11
|
+
License-Expression: Apache-2.0
|
|
12
|
+
License-File: LICENSE
|
|
13
|
+
License-File: NOTICE
|
|
14
|
+
Keywords: agents,ai,claude,mcp,model context protocol,stdio,taskadence
|
|
15
|
+
Classifier: Development Status :: 3 - Alpha
|
|
16
|
+
Classifier: Environment :: Console
|
|
17
|
+
Classifier: Intended Audience :: Developers
|
|
18
|
+
Classifier: Operating System :: OS Independent
|
|
19
|
+
Classifier: Programming Language :: Python :: 3
|
|
20
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
21
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
22
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
23
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
24
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
25
|
+
Classifier: Topic :: Office/Business :: Scheduling
|
|
26
|
+
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
|
|
27
|
+
Classifier: Typing :: Typed
|
|
28
|
+
Requires-Python: >=3.10
|
|
29
|
+
Requires-Dist: httpx<1,>=0.27
|
|
30
|
+
Requires-Dist: mcp<2,>=1.30
|
|
31
|
+
Provides-Extra: dev
|
|
32
|
+
Requires-Dist: anyio>=4; extra == 'dev'
|
|
33
|
+
Requires-Dist: build>=1.2; extra == 'dev'
|
|
34
|
+
Requires-Dist: mypy<2.4,>=1.11; extra == 'dev'
|
|
35
|
+
Requires-Dist: pip-audit>=2.7; extra == 'dev'
|
|
36
|
+
Requires-Dist: pytest>=8; extra == 'dev'
|
|
37
|
+
Requires-Dist: ruff==0.16.9; extra == 'dev'
|
|
38
|
+
Requires-Dist: starlette>=0.40; extra == 'dev'
|
|
39
|
+
Requires-Dist: twine>=5; extra == 'dev'
|
|
40
|
+
Description-Content-Type: text/markdown
|
|
41
|
+
|
|
42
|
+
# taskadence-mcp: TasKadence for AI assistants that start a local program
|
|
43
|
+
|
|
44
|
+
[](https://pypi.org/project/taskadence-mcp/)
|
|
45
|
+
[](https://pypi.org/project/taskadence-mcp/)
|
|
46
|
+
[](https://github.com/indrasol/taskadence-python/blob/main/LICENSE)
|
|
47
|
+
|
|
48
|
+
[TasKadence](https://taskadence.com) is task and project management for teams. `taskadence-mcp` lets an AI assistant
|
|
49
|
+
(Claude Desktop, Claude Code, Cursor, VS Code and others) read and update your TasKadence tasks, projects and teams,
|
|
50
|
+
through the Model Context Protocol (MCP).
|
|
51
|
+
|
|
52
|
+
**Do I need this, or the URL?** If your assistant can add an MCP server by URL (often called a remote server or a
|
|
53
|
+
custom connector), use the URL `https://api.taskadence.com/mcp` instead: you sign in with OAuth and there is no token
|
|
54
|
+
to manage. See [Connect](https://docs.taskadence.com/mcp/connect/). Use this package when your assistant can only start
|
|
55
|
+
a local program (a "stdio" server), or when you want it to use a token you created yourself.
|
|
56
|
+
|
|
57
|
+
Its twin on npm, `npx -y @taskadence/mcp`, does exactly the same with Node.js; pick whichever runtime you have.
|
|
58
|
+
|
|
59
|
+
> **`0.x` is a pre-release.** Any `0.x` release may change anything; pin a version in configs you depend on.
|
|
60
|
+
|
|
61
|
+
**Documentation:** [docs.taskadence.com](https://docs.taskadence.com/mcp/) ·
|
|
62
|
+
**Source:** [GitHub](https://github.com/indrasol/taskadence-python) · **Issues:** [GitHub issues](https://github.com/indrasol/taskadence-python/issues)
|
|
63
|
+
|
|
64
|
+
## Set up in 3 steps
|
|
65
|
+
|
|
66
|
+
You need a TasKadence account and about five minutes.
|
|
67
|
+
|
|
68
|
+
### 1. Get a token
|
|
69
|
+
|
|
70
|
+
A token is a password for programs: the assistant uses it to act for you in one organization.
|
|
71
|
+
|
|
72
|
+
1. In TasKadence, open **Developers** in the sidebar, stay on the **Tokens** tab and click **Create token**.
|
|
73
|
+
2. Give it a name you will recognise later (for example "Claude Desktop").
|
|
74
|
+
3. Under **Scopes**, tick what the assistant may do. For an assistant that only looks: **Read** on the **Tasks**,
|
|
75
|
+
**Projects** and **Teams** rows. To let it create and change things too: **Write** on those rows (Write includes
|
|
76
|
+
Read). The scopes decide which tools the assistant sees.
|
|
77
|
+
4. Click **Create token** and copy it (it starts with `tkd_live_`). **It is shown once.**
|
|
78
|
+
|
|
79
|
+
Shortcut: **Developers > MCP** in TasKadence writes the configuration for your client, with a new token already in it.
|
|
80
|
+
|
|
81
|
+
### 2. Install uv
|
|
82
|
+
|
|
83
|
+
`uvx` comes with [uv](https://docs.astral.sh/uv/getting-started/installation/), a Python tool runner. It downloads and
|
|
84
|
+
runs `taskadence-mcp` (and a suitable Python, if you have none) the first time your client starts it. Skip this step
|
|
85
|
+
if `uvx --version` already prints a version.
|
|
86
|
+
|
|
87
|
+
macOS or Linux:
|
|
88
|
+
|
|
89
|
+
```bash
|
|
90
|
+
curl -LsSf https://astral.sh/uv/install.sh | sh
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
Windows PowerShell:
|
|
94
|
+
|
|
95
|
+
```powershell
|
|
96
|
+
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
Prefer pip? `pip install taskadence-mcp` installs a `taskadence-mcp` command; then use `"command": "taskadence-mcp"`
|
|
100
|
+
and `"args": []` below. `taskadence-mcp --help` lists the options.
|
|
101
|
+
|
|
102
|
+
### 3. Add it to your client
|
|
103
|
+
|
|
104
|
+
Paste your token where the examples say `tkd_live_your_token_here`, then restart the client.
|
|
105
|
+
|
|
106
|
+
**Claude Desktop.** Open **Settings > Developer > Edit Config**. That opens `claude_desktop_config.json`, which lives
|
|
107
|
+
at `~/Library/Application Support/Claude/claude_desktop_config.json` on macOS and
|
|
108
|
+
`%APPDATA%\Claude\claude_desktop_config.json` on Windows. Add the `taskadence` entry (keep any other servers already
|
|
109
|
+
under `mcpServers`), save, then quit Claude Desktop completely and open it again.
|
|
110
|
+
|
|
111
|
+
```json
|
|
112
|
+
{
|
|
113
|
+
"mcpServers": {
|
|
114
|
+
"taskadence": {
|
|
115
|
+
"command": "uvx",
|
|
116
|
+
"args": ["taskadence-mcp"],
|
|
117
|
+
"env": { "TASKADENCE_TOKEN": "tkd_live_your_token_here" }
|
|
118
|
+
}
|
|
119
|
+
}
|
|
120
|
+
}
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
**Claude Code.** One command (add `--scope user` to use it in every project):
|
|
124
|
+
|
|
125
|
+
```bash
|
|
126
|
+
claude mcp add --env TASKADENCE_TOKEN=tkd_live_your_token_here --transport stdio taskadence -- uvx taskadence-mcp
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
**Cursor.** Put the same JSON as Claude Desktop in `~/.cursor/mcp.json` for every project
|
|
130
|
+
(`%USERPROFILE%\.cursor\mcp.json` on Windows), or in `.cursor/mcp.json` inside one project.
|
|
131
|
+
|
|
132
|
+
**VS Code.** Put this in `.vscode/mcp.json` in your workspace, or, for every workspace, run **MCP: Open User
|
|
133
|
+
Configuration** from the Command Palette. VS Code uses `servers` and `"type": "stdio"`:
|
|
134
|
+
|
|
135
|
+
```json
|
|
136
|
+
{
|
|
137
|
+
"servers": {
|
|
138
|
+
"taskadence": {
|
|
139
|
+
"type": "stdio",
|
|
140
|
+
"command": "uvx",
|
|
141
|
+
"args": ["taskadence-mcp"],
|
|
142
|
+
"env": { "TASKADENCE_TOKEN": "tkd_live_your_token_here" }
|
|
143
|
+
}
|
|
144
|
+
}
|
|
145
|
+
}
|
|
146
|
+
```
|
|
147
|
+
|
|
148
|
+
Keep tokens out of git: a project file (`.cursor/mcp.json`, `.vscode/mcp.json`) is easy to commit by mistake, so
|
|
149
|
+
prefer the user-level file for a config that holds a token.
|
|
150
|
+
|
|
151
|
+
## Check it works
|
|
152
|
+
|
|
153
|
+
Ask your assistant: *"Which TasKadence account and organization are you connected to?"* It should call the `whoami`
|
|
154
|
+
tool (your client may ask you to allow it first) and answer with your name and your organization. Then try *"List my
|
|
155
|
+
tasks that are in progress."*
|
|
156
|
+
|
|
157
|
+
Your client also lists its MCP servers: `taskadence` should be there, connected, with its tools (in Claude Code, type
|
|
158
|
+
`/mcp`). An error or an empty tool list means one of the problems below.
|
|
159
|
+
|
|
160
|
+
## Troubleshooting
|
|
161
|
+
|
|
162
|
+
- **"TASKADENCE_TOKEN is not set":** the `env` block is missing or the name is misspelled. Fix the config and restart
|
|
163
|
+
the client.
|
|
164
|
+
- **Token refused (401):** the error says "TasKadence refused the access token in TASKADENCE_TOKEN (401)". The token
|
|
165
|
+
was copied wrong, has expired or was revoked. Create a new one in **Developers > Tokens**, replace it in the config,
|
|
166
|
+
and restart the client.
|
|
167
|
+
- **A tool is missing, or "insufficient scope":** the token's scopes decide which tools appear. Create a token with
|
|
168
|
+
**Write** ticked to let the assistant change things (scopes cannot be added to an existing token).
|
|
169
|
+
`TASKADENCE_MCP_READONLY=1` hides every tool that writes, and `TASKADENCE_MCP_GROUPS` limits the tool groups (see
|
|
170
|
+
Configure below).
|
|
171
|
+
- **`uvx` not found (`spawn uvx ENOENT`):** install it (step 2), then restart the client. On macOS an app
|
|
172
|
+
opened from the Dock may not see your terminal's `PATH`: put the full path in `"command"` (find it with
|
|
173
|
+
`which uvx`; on Windows, `where uvx`).
|
|
174
|
+
- **Wrong Python 3.10 version:** `taskadence-mcp` needs Python 3.10 or later. Check with `python --version`.
|
|
175
|
+
- **"MCP server unreachable":** the computer cannot reach the TasKadence API. Check the network, and
|
|
176
|
+
`TASKADENCE_API_URL` if you set it.
|
|
177
|
+
|
|
178
|
+
Still stuck? Open a [GitHub issue](https://github.com/indrasol/taskadence-python/issues) with the error message and your client's name; never paste a live
|
|
179
|
+
token.
|
|
180
|
+
|
|
181
|
+
## Configure
|
|
182
|
+
|
|
183
|
+
Everything is optional except the token. Set these in the `env` block of your client's config, or pass the flags in
|
|
184
|
+
`args`.
|
|
185
|
+
|
|
186
|
+
| Variable | Flag | |
|
|
187
|
+
|---|---|---|
|
|
188
|
+
| `TASKADENCE_TOKEN` | none | **Required.** A personal access token (`tkd_live_…`). |
|
|
189
|
+
| `TASKADENCE_API_URL` | `--api-url` | The API's origin. Default: `https://api.taskadence.com`. `/mcp` is added. |
|
|
190
|
+
| `TASKADENCE_MCP_READONLY` | `--readonly` / `--no-readonly` | `1`: only tools that read, enforced by the server. |
|
|
191
|
+
| `TASKADENCE_MCP_GROUPS` | `--groups` | For example `tasks,projects`: only those tool groups. Default: every group except `admin`; `me` is always on. |
|
|
192
|
+
|
|
193
|
+
Flags win over the environment. There is no token flag: a command line is visible to every process on the machine.
|
|
194
|
+
The tools and groups are listed in [Tools](https://docs.taskadence.com/mcp/tools/).
|
|
195
|
+
|
|
196
|
+
## What it does, exactly
|
|
197
|
+
|
|
198
|
+
`taskadence-mcp` is a proxy, not a second server: it speaks MCP over stdio to your client and forwards every message to the
|
|
199
|
+
TasKadence remote MCP server (`<api>/mcp`, Streamable HTTP) with your token. The tools, the read-only and tool-group
|
|
200
|
+
enforcement, and the audit trail are the remote server's.
|
|
201
|
+
|
|
202
|
+
- stdin goes to the remote server unchanged (`initialize` included; the server is stateless), and the server's answers
|
|
203
|
+
go to stdout unchanged. stdout carries JSON-RPC and nothing else; diagnostics go to stderr, never the token.
|
|
204
|
+
- A refused token (401) is answered with a JSON-RPC error naming `TASKADENCE_TOKEN` (code `-32001`), any other HTTP
|
|
205
|
+
refusal with its status and the server's detail (`-32002`; an unknown group is a 400), an unreachable server with
|
|
206
|
+
`-32003`. Each also writes one line to stderr.
|
|
207
|
+
- It holds no tool of its own and reaches nothing but `<api>/mcp`.
|
|
208
|
+
|
|
209
|
+
## Requirements
|
|
210
|
+
|
|
211
|
+
Python 3.10 or later. Depends on `mcp` (the official MCP SDK, `<2`) and `httpx`.
|
|
212
|
+
|
|
213
|
+
## Support and security
|
|
214
|
+
|
|
215
|
+
Bugs and questions: [GitHub issues](https://github.com/indrasol/taskadence-python/issues); never paste a live token. Vulnerabilities: report them privately as
|
|
216
|
+
described in [SECURITY.md](https://github.com/indrasol/taskadence-python/blob/main/SECURITY.md) (GitHub private vulnerability reporting, or
|
|
217
|
+
srvcs.infra@indrasol.com).
|
|
218
|
+
|
|
219
|
+
## License
|
|
220
|
+
|
|
221
|
+
Apache License 2.0. See [LICENSE](https://github.com/indrasol/taskadence-python/blob/main/LICENSE). The license grants no right to use the TasKadence or
|
|
222
|
+
Indrasol names or marks.
|
|
@@ -0,0 +1,181 @@
|
|
|
1
|
+
# taskadence-mcp: TasKadence for AI assistants that start a local program
|
|
2
|
+
|
|
3
|
+
[](https://pypi.org/project/taskadence-mcp/)
|
|
4
|
+
[](https://pypi.org/project/taskadence-mcp/)
|
|
5
|
+
[](https://github.com/indrasol/taskadence-python/blob/main/LICENSE)
|
|
6
|
+
|
|
7
|
+
[TasKadence](https://taskadence.com) is task and project management for teams. `taskadence-mcp` lets an AI assistant
|
|
8
|
+
(Claude Desktop, Claude Code, Cursor, VS Code and others) read and update your TasKadence tasks, projects and teams,
|
|
9
|
+
through the Model Context Protocol (MCP).
|
|
10
|
+
|
|
11
|
+
**Do I need this, or the URL?** If your assistant can add an MCP server by URL (often called a remote server or a
|
|
12
|
+
custom connector), use the URL `https://api.taskadence.com/mcp` instead: you sign in with OAuth and there is no token
|
|
13
|
+
to manage. See [Connect](https://docs.taskadence.com/mcp/connect/). Use this package when your assistant can only start
|
|
14
|
+
a local program (a "stdio" server), or when you want it to use a token you created yourself.
|
|
15
|
+
|
|
16
|
+
Its twin on npm, `npx -y @taskadence/mcp`, does exactly the same with Node.js; pick whichever runtime you have.
|
|
17
|
+
|
|
18
|
+
> **`0.x` is a pre-release.** Any `0.x` release may change anything; pin a version in configs you depend on.
|
|
19
|
+
|
|
20
|
+
**Documentation:** [docs.taskadence.com](https://docs.taskadence.com/mcp/) ·
|
|
21
|
+
**Source:** [GitHub](https://github.com/indrasol/taskadence-python) · **Issues:** [GitHub issues](https://github.com/indrasol/taskadence-python/issues)
|
|
22
|
+
|
|
23
|
+
## Set up in 3 steps
|
|
24
|
+
|
|
25
|
+
You need a TasKadence account and about five minutes.
|
|
26
|
+
|
|
27
|
+
### 1. Get a token
|
|
28
|
+
|
|
29
|
+
A token is a password for programs: the assistant uses it to act for you in one organization.
|
|
30
|
+
|
|
31
|
+
1. In TasKadence, open **Developers** in the sidebar, stay on the **Tokens** tab and click **Create token**.
|
|
32
|
+
2. Give it a name you will recognise later (for example "Claude Desktop").
|
|
33
|
+
3. Under **Scopes**, tick what the assistant may do. For an assistant that only looks: **Read** on the **Tasks**,
|
|
34
|
+
**Projects** and **Teams** rows. To let it create and change things too: **Write** on those rows (Write includes
|
|
35
|
+
Read). The scopes decide which tools the assistant sees.
|
|
36
|
+
4. Click **Create token** and copy it (it starts with `tkd_live_`). **It is shown once.**
|
|
37
|
+
|
|
38
|
+
Shortcut: **Developers > MCP** in TasKadence writes the configuration for your client, with a new token already in it.
|
|
39
|
+
|
|
40
|
+
### 2. Install uv
|
|
41
|
+
|
|
42
|
+
`uvx` comes with [uv](https://docs.astral.sh/uv/getting-started/installation/), a Python tool runner. It downloads and
|
|
43
|
+
runs `taskadence-mcp` (and a suitable Python, if you have none) the first time your client starts it. Skip this step
|
|
44
|
+
if `uvx --version` already prints a version.
|
|
45
|
+
|
|
46
|
+
macOS or Linux:
|
|
47
|
+
|
|
48
|
+
```bash
|
|
49
|
+
curl -LsSf https://astral.sh/uv/install.sh | sh
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
Windows PowerShell:
|
|
53
|
+
|
|
54
|
+
```powershell
|
|
55
|
+
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
Prefer pip? `pip install taskadence-mcp` installs a `taskadence-mcp` command; then use `"command": "taskadence-mcp"`
|
|
59
|
+
and `"args": []` below. `taskadence-mcp --help` lists the options.
|
|
60
|
+
|
|
61
|
+
### 3. Add it to your client
|
|
62
|
+
|
|
63
|
+
Paste your token where the examples say `tkd_live_your_token_here`, then restart the client.
|
|
64
|
+
|
|
65
|
+
**Claude Desktop.** Open **Settings > Developer > Edit Config**. That opens `claude_desktop_config.json`, which lives
|
|
66
|
+
at `~/Library/Application Support/Claude/claude_desktop_config.json` on macOS and
|
|
67
|
+
`%APPDATA%\Claude\claude_desktop_config.json` on Windows. Add the `taskadence` entry (keep any other servers already
|
|
68
|
+
under `mcpServers`), save, then quit Claude Desktop completely and open it again.
|
|
69
|
+
|
|
70
|
+
```json
|
|
71
|
+
{
|
|
72
|
+
"mcpServers": {
|
|
73
|
+
"taskadence": {
|
|
74
|
+
"command": "uvx",
|
|
75
|
+
"args": ["taskadence-mcp"],
|
|
76
|
+
"env": { "TASKADENCE_TOKEN": "tkd_live_your_token_here" }
|
|
77
|
+
}
|
|
78
|
+
}
|
|
79
|
+
}
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
**Claude Code.** One command (add `--scope user` to use it in every project):
|
|
83
|
+
|
|
84
|
+
```bash
|
|
85
|
+
claude mcp add --env TASKADENCE_TOKEN=tkd_live_your_token_here --transport stdio taskadence -- uvx taskadence-mcp
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
**Cursor.** Put the same JSON as Claude Desktop in `~/.cursor/mcp.json` for every project
|
|
89
|
+
(`%USERPROFILE%\.cursor\mcp.json` on Windows), or in `.cursor/mcp.json` inside one project.
|
|
90
|
+
|
|
91
|
+
**VS Code.** Put this in `.vscode/mcp.json` in your workspace, or, for every workspace, run **MCP: Open User
|
|
92
|
+
Configuration** from the Command Palette. VS Code uses `servers` and `"type": "stdio"`:
|
|
93
|
+
|
|
94
|
+
```json
|
|
95
|
+
{
|
|
96
|
+
"servers": {
|
|
97
|
+
"taskadence": {
|
|
98
|
+
"type": "stdio",
|
|
99
|
+
"command": "uvx",
|
|
100
|
+
"args": ["taskadence-mcp"],
|
|
101
|
+
"env": { "TASKADENCE_TOKEN": "tkd_live_your_token_here" }
|
|
102
|
+
}
|
|
103
|
+
}
|
|
104
|
+
}
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
Keep tokens out of git: a project file (`.cursor/mcp.json`, `.vscode/mcp.json`) is easy to commit by mistake, so
|
|
108
|
+
prefer the user-level file for a config that holds a token.
|
|
109
|
+
|
|
110
|
+
## Check it works
|
|
111
|
+
|
|
112
|
+
Ask your assistant: *"Which TasKadence account and organization are you connected to?"* It should call the `whoami`
|
|
113
|
+
tool (your client may ask you to allow it first) and answer with your name and your organization. Then try *"List my
|
|
114
|
+
tasks that are in progress."*
|
|
115
|
+
|
|
116
|
+
Your client also lists its MCP servers: `taskadence` should be there, connected, with its tools (in Claude Code, type
|
|
117
|
+
`/mcp`). An error or an empty tool list means one of the problems below.
|
|
118
|
+
|
|
119
|
+
## Troubleshooting
|
|
120
|
+
|
|
121
|
+
- **"TASKADENCE_TOKEN is not set":** the `env` block is missing or the name is misspelled. Fix the config and restart
|
|
122
|
+
the client.
|
|
123
|
+
- **Token refused (401):** the error says "TasKadence refused the access token in TASKADENCE_TOKEN (401)". The token
|
|
124
|
+
was copied wrong, has expired or was revoked. Create a new one in **Developers > Tokens**, replace it in the config,
|
|
125
|
+
and restart the client.
|
|
126
|
+
- **A tool is missing, or "insufficient scope":** the token's scopes decide which tools appear. Create a token with
|
|
127
|
+
**Write** ticked to let the assistant change things (scopes cannot be added to an existing token).
|
|
128
|
+
`TASKADENCE_MCP_READONLY=1` hides every tool that writes, and `TASKADENCE_MCP_GROUPS` limits the tool groups (see
|
|
129
|
+
Configure below).
|
|
130
|
+
- **`uvx` not found (`spawn uvx ENOENT`):** install it (step 2), then restart the client. On macOS an app
|
|
131
|
+
opened from the Dock may not see your terminal's `PATH`: put the full path in `"command"` (find it with
|
|
132
|
+
`which uvx`; on Windows, `where uvx`).
|
|
133
|
+
- **Wrong Python 3.10 version:** `taskadence-mcp` needs Python 3.10 or later. Check with `python --version`.
|
|
134
|
+
- **"MCP server unreachable":** the computer cannot reach the TasKadence API. Check the network, and
|
|
135
|
+
`TASKADENCE_API_URL` if you set it.
|
|
136
|
+
|
|
137
|
+
Still stuck? Open a [GitHub issue](https://github.com/indrasol/taskadence-python/issues) with the error message and your client's name; never paste a live
|
|
138
|
+
token.
|
|
139
|
+
|
|
140
|
+
## Configure
|
|
141
|
+
|
|
142
|
+
Everything is optional except the token. Set these in the `env` block of your client's config, or pass the flags in
|
|
143
|
+
`args`.
|
|
144
|
+
|
|
145
|
+
| Variable | Flag | |
|
|
146
|
+
|---|---|---|
|
|
147
|
+
| `TASKADENCE_TOKEN` | none | **Required.** A personal access token (`tkd_live_…`). |
|
|
148
|
+
| `TASKADENCE_API_URL` | `--api-url` | The API's origin. Default: `https://api.taskadence.com`. `/mcp` is added. |
|
|
149
|
+
| `TASKADENCE_MCP_READONLY` | `--readonly` / `--no-readonly` | `1`: only tools that read, enforced by the server. |
|
|
150
|
+
| `TASKADENCE_MCP_GROUPS` | `--groups` | For example `tasks,projects`: only those tool groups. Default: every group except `admin`; `me` is always on. |
|
|
151
|
+
|
|
152
|
+
Flags win over the environment. There is no token flag: a command line is visible to every process on the machine.
|
|
153
|
+
The tools and groups are listed in [Tools](https://docs.taskadence.com/mcp/tools/).
|
|
154
|
+
|
|
155
|
+
## What it does, exactly
|
|
156
|
+
|
|
157
|
+
`taskadence-mcp` is a proxy, not a second server: it speaks MCP over stdio to your client and forwards every message to the
|
|
158
|
+
TasKadence remote MCP server (`<api>/mcp`, Streamable HTTP) with your token. The tools, the read-only and tool-group
|
|
159
|
+
enforcement, and the audit trail are the remote server's.
|
|
160
|
+
|
|
161
|
+
- stdin goes to the remote server unchanged (`initialize` included; the server is stateless), and the server's answers
|
|
162
|
+
go to stdout unchanged. stdout carries JSON-RPC and nothing else; diagnostics go to stderr, never the token.
|
|
163
|
+
- A refused token (401) is answered with a JSON-RPC error naming `TASKADENCE_TOKEN` (code `-32001`), any other HTTP
|
|
164
|
+
refusal with its status and the server's detail (`-32002`; an unknown group is a 400), an unreachable server with
|
|
165
|
+
`-32003`. Each also writes one line to stderr.
|
|
166
|
+
- It holds no tool of its own and reaches nothing but `<api>/mcp`.
|
|
167
|
+
|
|
168
|
+
## Requirements
|
|
169
|
+
|
|
170
|
+
Python 3.10 or later. Depends on `mcp` (the official MCP SDK, `<2`) and `httpx`.
|
|
171
|
+
|
|
172
|
+
## Support and security
|
|
173
|
+
|
|
174
|
+
Bugs and questions: [GitHub issues](https://github.com/indrasol/taskadence-python/issues); never paste a live token. Vulnerabilities: report them privately as
|
|
175
|
+
described in [SECURITY.md](https://github.com/indrasol/taskadence-python/blob/main/SECURITY.md) (GitHub private vulnerability reporting, or
|
|
176
|
+
srvcs.infra@indrasol.com).
|
|
177
|
+
|
|
178
|
+
## License
|
|
179
|
+
|
|
180
|
+
Apache License 2.0. See [LICENSE](https://github.com/indrasol/taskadence-python/blob/main/LICENSE). The license grants no right to use the TasKadence or
|
|
181
|
+
Indrasol names or marks.
|