{"_id":"asana-gate","_rev":"12-bd74198274c2fcb039c1c3200ac8a092","name":"asana-gate","dist-tags":{"latest":"0.4.1"},"versions":{"0.1.0":{"name":"asana-gate","version":"0.1.0","keywords":["access-control","agent","asana","gateway","mcp","model-context-protocol","policy"],"license":"Apache-2.0","_id":"asana-gate@0.1.0","maintainers":[{"name":"sincekmori","email":"sincekmori@gmail.com"}],"homepage":"https://github.com/sincekmori/asana-gate#readme","bugs":{"url":"https://github.com/sincekmori/asana-gate/issues"},"bin":{"asana-gate":"./dist/cli.mjs"},"dist":{"shasum":"e33005cb7f2693b71ea337bdf44ede8faf322c2e","tarball":"https://registry.npmjs.org/asana-gate/-/asana-gate-0.1.0.tgz","fileCount":63,"integrity":"sha512-gURYonbsylYha1E9EQRaXNAcaAXOO3I0BMdXRhGrjgB07KPhkRCUO9to8hTM05DxJzzOVT30EPWO1V2fJEnjxA==","signatures":[{"sig":"MEUCIQCSe8LLVluyMEMwkLFbdV1nIUE9E36V9QfvbbFwKaziRwIgZxavAGaVKjiuzFgpar1GlkCfVeTNits8X87QRcrqotU=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIFyVqD1GV+z9REyQj/t6IiWRmIgzjLS/WeN53P2nuIKHAiEAkWDd/sY/EnLQzrFMcN36T7FCOpe+4cFDwYz8zEIRcD8=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/asana-gate@0.1.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":4310231},"main":"./dist/index.cjs","type":"module","types":"./dist/index.d.cts","module":"./dist/index.mjs","engines":{"node":">=24","pnpm":">=12"},"exports":{".":{"import":"./dist/index.mjs","require":"./dist/index.cjs"},"./schema.json":"./schema.json","./package.json":"./package.json","./settings.schema.json":"./settings.schema.json"},"scripts":{"dev":"tsdown --watch","lint":"oxlint --type-aware","test":"vitest run","build":"tsdown","format":"oxfmt --write .","release":"changeset publish","version":"changeset version && pnpm generate-skill","changeset":"changeset","typecheck":"tsc --noEmit","check:skill":"skills-ref validate skills/asana-gate","docs-updates":"node scripts/docs-updates.ts","format:check":"oxfmt --check .","sync-openapi":"node scripts/sync-openapi.ts","generate-skill":"node scripts/generate-skill.ts","generate-schema":"node scripts/generate-schema.ts"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"0f0b93be-d2c6-4ac0-bcd7-a4559b69a366"}},"repository":{"url":"git+https://github.com/sincekmori/asana-gate.git","type":"git"},"description":"Declarative access-control policy in front of the Asana API, served to AI agents over MCP.","directories":{},"sideEffects":false,"dependencies":{"zod":"^4.6.7","yaml":"^2.9.1","@modelcontextprotocol/node":"^2.1.2","@modelcontextprotocol/server":"^2.4.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"oxfmt":"^0.75.0","oxlint":"^1.89.0","tsdown":"^0.23.4","vitest":"^5.1.0","publint":"^0.3.25","skills-ref":"^0.1.5","typescript":"^7.0.2","@types/node":"^26.6.6","@changesets/cli":"^3.0.3","oxlint-tsgolint":"^7.0.2004","@arethetypeswrong/core":"^0.18.5","@modelcontextprotocol/client":"^2.4.0"},"_npmOperationalInternal":{"tmp":"tmp/asana-gate_0.1.0_1793794744050_0.5974506836235918","host":"s3://npm-registry-packages-npm-production"}},"0.1.1":{"name":"asana-gate","version":"0.1.1","keywords":["access-control","agent","asana","gateway","mcp","model-context-protocol","policy"],"license":"Apache-2.0","_id":"asana-gate@0.1.1","maintainers":[{"name":"sincekmori","email":"sincekmori@gmail.com"}],"homepage":"https://github.com/sincekmori/asana-gate#readme","bugs":{"url":"https://github.com/sincekmori/asana-gate/issues"},"bin":{"asana-gate":"./dist/cli.mjs"},"dist":{"shasum":"ccc55463e06b2f323054c11934d78be109387810","tarball":"https://registry.npmjs.org/asana-gate/-/asana-gate-0.1.1.tgz","fileCount":38,"integrity":"sha512-vx0W70+iy05HdkfAu6OPl/6bJbeX/pzwpfiAA202C6CPuQzEvDSIRcR5XYCZPLNrcm1DMtXpGuP1/79F7mRCuQ==","signatures":[{"sig":"MEYCIQCMkZKmZ/9W5geIIYbnk8orpZmw+agbY/1rvLaki+WVaQIhALKXNe47S32yBS8QVdIpc6caLt89j5VASQjCT4AERhOX","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQD/9CETcWTyIKUXVCt+ovksIM6NlKI4cmXQxdbxIakUcQIhAI4ro9aMN+Bo4BfBfR4ZACWMDx/XFpuf/JTT7QiNW09D","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/asana-gate@0.1.1","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":1843304},"main":"./dist/index.cjs","type":"module","types":"./dist/index.d.cts","module":"./dist/index.mjs","engines":{"node":">=24","pnpm":">=12"},"exports":{".":{"import":"./dist/index.mjs","require":"./dist/index.cjs"},"./schema.json":"./schema.json","./package.json":"./package.json","./settings.schema.json":"./settings.schema.json"},"scripts":{"dev":"tsdown --watch","lint":"oxlint --type-aware","test":"vitest run","build":"tsdown","format":"oxfmt --write .","release":"changeset publish","version":"changeset version && pnpm generate-skill","changeset":"changeset","typecheck":"tsc --noEmit","check:skill":"skills-ref validate skills/asana-gate","docs-updates":"node scripts/docs-updates.ts","format:check":"oxfmt --check .","sync-openapi":"node scripts/sync-openapi.ts","generate-skill":"node scripts/generate-skill.ts","generate-schema":"node scripts/generate-schema.ts"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"0f0b93be-d2c6-4ac0-bcd7-a4559b69a366"}},"repository":{"url":"git+https://github.com/sincekmori/asana-gate.git","type":"git"},"description":"Declarative access-control policy in front of the Asana API, served to AI agents over MCP.","directories":{},"sideEffects":false,"dependencies":{"zod":"^4.6.7","yaml":"^2.9.1","@modelcontextprotocol/node":"^2.1.2","@modelcontextprotocol/server":"^2.4.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"oxfmt":"^0.76.0","oxlint":"^1.89.0","tsdown":"^0.23.4","vitest":"^5.1.0","publint":"^0.3.25","skills-ref":"^0.1.5","typescript":"^7.0.2","@types/node":"^26.6.6","@changesets/cli":"^3.0.3","oxlint-tsgolint":"^7.0.2004","@arethetypeswrong/core":"^0.18.5","@modelcontextprotocol/client":"^2.4.0"},"_npmOperationalInternal":{"tmp":"tmp/asana-gate_0.1.1_1793795759110_0.030456707084003387","host":"s3://npm-registry-packages-npm-production"}},"0.2.0":{"name":"asana-gate","version":"0.2.0","keywords":["access-control","agent","asana","gateway","mcp","model-context-protocol","policy"],"license":"Apache-2.0","_id":"asana-gate@0.2.0","maintainers":[{"name":"sincekmori","email":"sincekmori@gmail.com"}],"homepage":"https://github.com/sincekmori/asana-gate#readme","bugs":{"url":"https://github.com/sincekmori/asana-gate/issues"},"bin":{"asana-gate":"./dist/cli.mjs"},"dist":{"shasum":"5c0cbc9893945f0dd25a381c0e034858d5a3a8c2","tarball":"https://registry.npmjs.org/asana-gate/-/asana-gate-0.2.0.tgz","fileCount":38,"integrity":"sha512-TERvn3XiZHiJXaKxUqJJacnHGx85sIfwktHShzsWUC+Pj+xr3fL9eT67KYu58LDkbvbWtg5e1AubAzDzOiZktg==","signatures":[{"sig":"MEUCIQDJfbXOJKztcOR+Dw9aj4L97PfufVOUhYgN74Tfahi0OQIgGVL8VBZhvZA8tTSTgExJXlSQYz5FfdPBqnhNlt+8cLQ=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQC/1SF13VTh3ObBpnWpBxGrRiJEX4WUmowiZYLOEvgRjAIgA8EZRGrp5cymB51ggRPu5C6OpwEwvYprTfN0k/c+hQ4=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/asana-gate@0.2.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":1868525},"main":"./dist/index.cjs","type":"module","types":"./dist/index.d.cts","module":"./dist/index.mjs","engines":{"node":">=24","pnpm":">=12"},"exports":{".":{"import":"./dist/index.mjs","require":"./dist/index.cjs"},"./schema.json":"./schema.json","./package.json":"./package.json","./settings.schema.json":"./settings.schema.json"},"scripts":{"dev":"tsdown --watch","lint":"oxlint --type-aware","test":"vitest run","build":"tsdown","format":"oxfmt --write .","release":"changeset publish","version":"changeset version && pnpm generate-skill","changeset":"changeset","typecheck":"tsc --noEmit","check:skill":"skills-ref validate skills/asana-gate","docs-updates":"node scripts/docs-updates.ts","format:check":"oxfmt --check .","sync-openapi":"node scripts/sync-openapi.ts","generate-skill":"node scripts/generate-skill.ts","generate-schema":"node scripts/generate-schema.ts"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"0f0b93be-d2c6-4ac0-bcd7-a4559b69a366"}},"repository":{"url":"git+https://github.com/sincekmori/asana-gate.git","type":"git"},"description":"Declarative access-control policy in front of the Asana API, served to AI agents over MCP.","directories":{},"sideEffects":false,"dependencies":{"zod":"^4.6.7","yaml":"^2.9.1","@modelcontextprotocol/node":"^2.1.2","@modelcontextprotocol/server":"^2.4.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"oxfmt":"^0.76.0","oxlint":"^1.89.0","tsdown":"^0.23.4","vitest":"^5.1.0","publint":"^0.3.25","skills-ref":"^0.1.5","typescript":"^7.0.2","@types/node":"^26.6.6","@changesets/cli":"^3.0.3","oxlint-tsgolint":"^7.0.2004","@arethetypeswrong/core":"^0.18.5","@modelcontextprotocol/client":"^2.4.0"},"_npmOperationalInternal":{"tmp":"tmp/asana-gate_0.2.0_1793844736601_0.7715784989098116","host":"s3://npm-registry-packages-npm-production"}},"0.3.0":{"name":"asana-gate","version":"0.3.0","keywords":["access-control","agent","asana","gateway","mcp","model-context-protocol","policy"],"license":"Apache-2.0","_id":"asana-gate@0.3.0","maintainers":[{"name":"sincekmori","email":"sincekmori@gmail.com"}],"homepage":"https://github.com/sincekmori/asana-gate#readme","bugs":{"url":"https://github.com/sincekmori/asana-gate/issues"},"bin":{"asana-gate":"./dist/cli.mjs"},"dist":{"shasum":"d82429e5ba6c182084ae5aa1e769c4626bcd42d9","tarball":"https://registry.npmjs.org/asana-gate/-/asana-gate-0.3.0.tgz","fileCount":38,"integrity":"sha512-ni7H2Vogj8289XdoK/bxvpBzq9TcmKBMnu4QuiiSw0K0NwLaD0zKORPqfvNr7+MKhcDp/Z129tVTPEWRegeJWw==","signatures":[{"sig":"MEUCIQCx0Orpq2CO8RMWcDTzzzYilxzsv1Z6tsooHLprUWlKNgIgc1Y2Pte4yOUlMr0NdysUDynoheycpP8R9LXE0Vs5jOA=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIDaFJOjIN2H3Vm7+ouGOHYTwkkyIThGxXV4HjJiP0bcaAiEA/SFvReOSFIXNJDpZpzKGirLZndK6xN3d9md2JK19yJc=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/asana-gate@0.3.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":1897425},"main":"./dist/index.cjs","type":"module","types":"./dist/index.d.cts","module":"./dist/index.mjs","engines":{"node":">=24","pnpm":">=12"},"exports":{".":{"import":"./dist/index.mjs","require":"./dist/index.cjs"},"./schema.json":"./schema.json","./package.json":"./package.json","./settings.schema.json":"./settings.schema.json"},"scripts":{"dev":"tsdown --watch","lint":"oxlint --type-aware","test":"vitest run","build":"tsdown","format":"oxfmt --write .","release":"changeset publish","version":"changeset version && pnpm generate-skill","changeset":"changeset","typecheck":"tsc --noEmit","check:skill":"skills-ref validate skills/asana-gate","docs-updates":"node scripts/docs-updates.ts","format:check":"oxfmt --check .","sync-openapi":"node scripts/sync-openapi.ts","generate-skill":"node scripts/generate-skill.ts","generate-schema":"node scripts/generate-schema.ts"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"0f0b93be-d2c6-4ac0-bcd7-a4559b69a366"}},"repository":{"url":"git+https://github.com/sincekmori/asana-gate.git","type":"git"},"description":"Declarative access-control policy in front of the Asana API, served to AI agents over MCP.","directories":{},"sideEffects":false,"dependencies":{"zod":"^4.6.7","yaml":"^2.9.1","jsonc-parser":"^3.3.1","@modelcontextprotocol/node":"^2.1.2","@modelcontextprotocol/server":"^2.4.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"oxfmt":"^0.76.0","oxlint":"^1.89.0","tsdown":"^0.23.4","vitest":"^5.1.0","publint":"^0.3.25","skills-ref":"^0.1.5","typescript":"^7.0.2","@types/node":"^26.6.6","@changesets/cli":"^3.0.3","oxlint-tsgolint":"^7.0.2004","@arethetypeswrong/core":"^0.18.5","@modelcontextprotocol/client":"^2.4.0"},"_npmOperationalInternal":{"tmp":"tmp/asana-gate_0.3.0_1793975187755_0.5347425680532164","host":"s3://npm-registry-packages-npm-production"}},"0.3.1":{"name":"asana-gate","version":"0.3.1","keywords":["access-control","agent","asana","gateway","mcp","model-context-protocol","policy"],"license":"Apache-2.0","_id":"asana-gate@0.3.1","maintainers":[{"name":"sincekmori","email":"sincekmori@gmail.com"}],"homepage":"https://github.com/sincekmori/asana-gate#readme","bugs":{"url":"https://github.com/sincekmori/asana-gate/issues"},"bin":{"asana-gate":"./dist/cli.mjs"},"dist":{"shasum":"cf72093eb3e590795bb74007f2f02b3b0e53376d","tarball":"https://registry.npmjs.org/asana-gate/-/asana-gate-0.3.1.tgz","fileCount":38,"integrity":"sha512-P7UWBFRjTJUTESwEUOxlpfLJD9RS0QAlYB0Rdg5zSc1HJkThxJnLMlD4B0+7Gz6KKbgVzmdsbzOIPiV26LcN7Q==","signatures":[{"sig":"MEYCIQCUVhoSbQ1yZdinzNo8mO0cUrsCnJfLRSoMrHwYKsxWvQIhAOg3u+DmMsvZ7gaVInYZSJswfQmBe4Nz7R3SxkF/GuHp","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQDg24PgBDgNGYHN7RALavRfA3HGXvyh2+7uAuaBY/Z0GAIhALmAPEgjlf/YX04FaQYvz9/C0GOe8AYkqprlSU5hVfr+","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/asana-gate@0.3.1","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":1897833},"main":"./dist/index.cjs","type":"module","types":"./dist/index.d.cts","module":"./dist/index.mjs","engines":{"node":">=24","pnpm":">=12"},"exports":{".":{"import":"./dist/index.mjs","require":"./dist/index.cjs"},"./schema.json":"./schema.json","./package.json":"./package.json","./settings.schema.json":"./settings.schema.json"},"mcpName":"io.github.sincekmori/asana-gate","scripts":{"dev":"tsdown --watch","lint":"oxlint --type-aware","test":"vitest run","build":"tsdown","format":"oxfmt --write .","release":"changeset publish","version":"changeset version && pnpm generate-server && pnpm generate-skill","changeset":"changeset","typecheck":"tsc --noEmit","check:skill":"skills-ref validate skills/asana-gate","docs-updates":"node scripts/docs-updates.ts","format:check":"oxfmt --check .","sync-openapi":"node scripts/sync-openapi.ts","generate-skill":"node scripts/generate-skill.ts","generate-schema":"node scripts/generate-schema.ts","generate-server":"node scripts/generate-server.ts"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"0f0b93be-d2c6-4ac0-bcd7-a4559b69a366"}},"repository":{"url":"git+https://github.com/sincekmori/asana-gate.git","type":"git"},"description":"Declarative access-control policy in front of the Asana API, served to AI agents over MCP.","directories":{},"sideEffects":false,"dependencies":{"zod":"^4.6.7","yaml":"^2.9.1","jsonc-parser":"^3.3.1","@modelcontextprotocol/node":"^2.1.2","@modelcontextprotocol/server":"^2.4.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"oxfmt":"^0.78.0","oxlint":"^1.89.0","tsdown":"^0.23.4","vitest":"^5.1.0","publint":"^0.3.25","skills-ref":"^0.1.5","typescript":"^7.0.2","@types/node":"^26.6.6","@changesets/cli":"^3.0.3","oxlint-tsgolint":"^7.0.2004","@arethetypeswrong/core":"^0.18.5","@modelcontextprotocol/client":"^2.4.0"},"_npmOperationalInternal":{"tmp":"tmp/asana-gate_0.3.1_1794454033880_0.2197817702058168","host":"s3://npm-registry-packages-npm-production"}},"0.3.2":{"name":"asana-gate","version":"0.3.2","keywords":["access-control","agent","asana","gateway","mcp","model-context-protocol","policy"],"license":"Apache-2.0","_id":"asana-gate@0.3.2","maintainers":[{"name":"sincekmori","email":"sincekmori@gmail.com"}],"homepage":"https://github.com/sincekmori/asana-gate#readme","bugs":{"url":"https://github.com/sincekmori/asana-gate/issues"},"bin":{"asana-gate":"./dist/cli.mjs"},"dist":{"shasum":"99f82bb3761d00709cbe614e705c416fff6e15e2","tarball":"https://registry.npmjs.org/asana-gate/-/asana-gate-0.3.2.tgz","fileCount":38,"integrity":"sha512-EvYXsu5FRdjLQ0lAEjVopZwNWcKvTBWojj7QhiJO+pwyBE67YgTMNGRbA1hM7ZGhdXXeUYlNnqtIA5YTf0yOMQ==","signatures":[{"sig":"MEQCIHb4JBa06kBy1N2gd1K/GP5bRPjZ+xDXiGtCBLVBZjvWAiBKlcmlpIpAnICbGFRBITERMv3xOWCHXvPOdgW+TEzMdQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQCb53C5fsMoJwVEtvHZcThWEm5b+Wpn+SnSXDrHRJN8EgIgQs0P/s9N3FISg5H8ry96GgjPjBjJynhQq8HyLRCcZaA=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/asana-gate@0.3.2","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":1898104},"main":"./dist/index.cjs","type":"module","types":"./dist/index.d.cts","module":"./dist/index.mjs","engines":{"node":">=24","pnpm":">=12"},"exports":{".":{"import":"./dist/index.mjs","require":"./dist/index.cjs"},"./schema.json":"./schema.json","./package.json":"./package.json","./settings.schema.json":"./settings.schema.json"},"mcpName":"io.github.sincekmori/asana-gate","scripts":{"dev":"tsdown --watch","lint":"oxlint --type-aware","test":"vitest run","build":"tsdown","format":"oxfmt --write .","release":"changeset publish","version":"changeset version && pnpm generate-server && pnpm generate-skill","changeset":"changeset","typecheck":"tsc --noEmit","check:skill":"skills-ref validate skills/asana-gate","docs-updates":"node scripts/docs-updates.ts","format:check":"oxfmt --check .","sync-openapi":"node scripts/sync-openapi.ts","generate-skill":"node scripts/generate-skill.ts","generate-schema":"node scripts/generate-schema.ts","generate-server":"node scripts/generate-server.ts"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"0f0b93be-d2c6-4ac0-bcd7-a4559b69a366"}},"repository":{"url":"git+https://github.com/sincekmori/asana-gate.git","type":"git"},"description":"Declarative access-control policy in front of the Asana API, served to AI agents over MCP.","directories":{},"sideEffects":false,"dependencies":{"zod":"^4.6.7","yaml":"^2.9.1","jsonc-parser":"^3.3.1","@modelcontextprotocol/node":"^2.1.2","@modelcontextprotocol/server":"^2.4.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"oxfmt":"^0.78.0","oxlint":"^1.89.0","tsdown":"^0.23.4","vitest":"^5.1.0","publint":"^0.3.25","skills-ref":"^0.1.5","typescript":"^7.0.2","@types/node":"^26.6.6","@changesets/cli":"^3.0.3","oxlint-tsgolint":"^7.0.2004","@arethetypeswrong/core":"^0.18.5","@modelcontextprotocol/client":"^2.4.0"},"_npmOperationalInternal":{"tmp":"tmp/asana-gate_0.3.2_1794543378374_0.5387878931609473","host":"s3://npm-registry-packages-npm-production"}},"0.4.0":{"name":"asana-gate","version":"0.4.0","keywords":["access-control","agent","asana","gateway","mcp","model-context-protocol","policy"],"license":"Apache-2.0","_id":"asana-gate@0.4.0","maintainers":[{"name":"sincekmori","email":"sincekmori@gmail.com"}],"homepage":"https://github.com/sincekmori/asana-gate#readme","bugs":{"url":"https://github.com/sincekmori/asana-gate/issues"},"bin":{"asana-gate":"./dist/cli.mjs"},"dist":{"shasum":"4e6d249b91663140cebc5a43068031c270f0f705","tarball":"https://registry.npmjs.org/asana-gate/-/asana-gate-0.4.0.tgz","fileCount":38,"integrity":"sha512-UG8qBVemHzJGjmgz05wLEfZkELr6Ex+1EVw3gSYNDib5uQHJTmEZShcYt9DfuXcZcRC4ONhRg4mZ0K28IZ2wAA==","signatures":[{"sig":"MEUCIBBOD8fUo3c0vqIPvb9P+5w5OvVrC39L4GbfdgkNRrPNAiEAhsLLqet2nPvitTuVvYm/4RBxqOiiWvo2K80rG4w/3o0=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQCAvIbBbhm1QVFMHBeQaZFUV5V24M2UnBSa8ssrLEcIYQIhAJXgipF7kWylpuEClyJmv7AakKLUUBGO4mM6iJTNjGLT","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/asana-gate@0.4.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":2025725},"main":"./dist/index.cjs","type":"module","types":"./dist/index.d.cts","module":"./dist/index.mjs","engines":{"node":">=24","pnpm":">=12"},"exports":{".":{"import":"./dist/index.mjs","require":"./dist/index.cjs"},"./schema.json":"./schema.json","./package.json":"./package.json","./settings.schema.json":"./settings.schema.json"},"mcpName":"io.github.sincekmori/asana-gate","scripts":{"dev":"tsdown --watch","lint":"oxlint --type-aware","test":"vitest run","build":"tsdown","format":"oxfmt --write .","release":"changeset publish","version":"changeset version && pnpm generate-server && pnpm generate-skill","changeset":"changeset","typecheck":"tsc --noEmit","check:skill":"skills-ref validate skills/asana-gate","docs-updates":"node scripts/docs-updates.ts","format:check":"oxfmt --check .","sync-openapi":"node scripts/sync-openapi.ts","generate-skill":"node scripts/generate-skill.ts","generate-schema":"node scripts/generate-schema.ts","generate-server":"node scripts/generate-server.ts"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"0f0b93be-d2c6-4ac0-bcd7-a4559b69a366"}},"repository":{"url":"git+https://github.com/sincekmori/asana-gate.git","type":"git"},"description":"Declarative access-control policy in front of the Asana API, served to AI agents over MCP.","directories":{},"sideEffects":false,"dependencies":{"zod":"^4.6.7","yaml":"^2.9.1","jsonc-parser":"^3.3.1","@modelcontextprotocol/node":"^2.1.2","@modelcontextprotocol/server":"^2.4.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"oxfmt":"^0.78.0","oxlint":"^1.89.0","tsdown":"^0.23.4","vitest":"^5.1.0","publint":"^0.3.25","skills-ref":"^0.1.5","typescript":"^7.0.2","@types/node":"^26.6.6","@changesets/cli":"^3.0.3","oxlint-tsgolint":"^7.0.2004","@arethetypeswrong/core":"^0.18.5","@modelcontextprotocol/client":"^2.4.0"},"_npmOperationalInternal":{"tmp":"tmp/asana-gate_0.4.0_1794830603584_0.667604345787201","host":"s3://npm-registry-packages-npm-production"}},"0.4.1":{"_id":"asana-gate@0.4.1","bin":{"asana-gate":"./dist/cli.mjs"},"bugs":{"url":"https://github.com/sincekmori/asana-gate/issues"},"dist":{"shasum":"984f81819fa91bc3e60eeeb227731501e22a3d99","tarball":"https://registry.npmjs.org/asana-gate/-/asana-gate-0.4.1.tgz","fileCount":38,"integrity":"sha512-PkuWTfdmXF12WMpPNsWUCmpjFfUuBK0HLE3AkbfZ0AMyuWeXhbWoBR5hqVdUL6mRmubaBVpIIG3HndwwbTNXtg==","signatures":[{"sig":"MEQCIFvBtdW/cpZfPbhZTutvBqcivzpVsDxVqIwfeWTy29kTAiBRmM+KQixo+7gWCGTIbykR3Ccewr0FExv+lbBDS3baqQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEQCIBO2Qs2+FwZMNgxKTDRAVba85i4xnRjbgZ/1sMYMi0DcAiA6kGecdZDaq8GsYktxjjlHA+VpeazUffW0CocBeZ3knQ=="}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/asana-gate@0.4.1","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":2026912},"main":"./dist/index.cjs","name":"asana-gate","type":"module","types":"./dist/index.d.cts","module":"./dist/index.mjs","engines":{"node":">=24","pnpm":">=12"},"exports":{".":{"import":"./dist/index.mjs","require":"./dist/index.cjs"},"./schema.json":"./schema.json","./package.json":"./package.json","./settings.schema.json":"./settings.schema.json"},"license":"Apache-2.0","mcpName":"io.github.sincekmori/asana-gate","scripts":{"dev":"tsdown --watch","lint":"oxlint --type-aware","test":"vitest run","build":"tsdown","format":"oxfmt --write .","release":"changeset publish","version":"changeset version && pnpm generate-server && pnpm generate-skill","changeset":"changeset","typecheck":"tsc --noEmit","check:skill":"skills-ref validate skills/asana-gate","docs-updates":"node scripts/docs-updates.ts","format:check":"oxfmt --check .","sync-openapi":"node scripts/sync-openapi.ts","generate-skill":"node scripts/generate-skill.ts","generate-schema":"node scripts/generate-schema.ts","generate-server":"node scripts/generate-server.ts"},"version":"0.4.1","_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"0f0b93be-d2c6-4ac0-bcd7-a4559b69a366"}},"homepage":"https://github.com/sincekmori/asana-gate#readme","keywords":["access-control","agent","asana","gateway","mcp","model-context-protocol","policy"],"repository":{"url":"git+https://github.com/sincekmori/asana-gate.git","type":"git"},"description":"Declarative access-control policy in front of the Asana API, served to AI agents over MCP.","directories":{},"maintainers":[{"name":"sincekmori","email":"sincekmori@gmail.com"}],"sideEffects":false,"dependencies":{"zod":"^4.6.7","yaml":"^2.9.1","jsonc-parser":"^3.3.1","@modelcontextprotocol/node":"^2.1.2","@modelcontextprotocol/server":"^2.4.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"oxfmt":"^0.78.0","oxlint":"^1.89.0","tsdown":"^0.23.4","vitest":"^5.1.0","publint":"^0.3.25","skills-ref":"^0.1.5","typescript":"^7.0.2","@types/node":"^26.6.6","@changesets/cli":"^3.0.3","oxlint-tsgolint":"^7.0.2004","@arethetypeswrong/core":"^0.18.5","@modelcontextprotocol/client":"^2.4.0"},"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/asana-gate_0.4.1_1794843558546_0.2639054003236554"}}},"time":{"created":"2026-11-04T11:52:04.575Z","modified":"2026-11-16T15:39:19.193Z","0.0.0-stage":"2026-11-04T11:52:04.575Z","0.0.0":"2026-11-04T11:54:12.986Z","0.1.0":"2026-11-04T12:19:04.181Z","0.1.1":"2026-11-04T12:35:59.226Z","0.2.0":"2026-11-05T02:12:17.080Z","0.3.0":"2026-11-06T14:26:27.881Z","0.3.1":"2026-11-12T03:27:14.007Z","0.3.2":"2026-11-13T04:16:18.513Z","0.4.0":"2026-11-16T12:03:23.727Z","0.4.1":"2026-11-16T15:39:18.745Z"},"bugs":{"url":"https://github.com/sincekmori/asana-gate/issues"},"license":"Apache-2.0","homepage":"https://github.com/sincekmori/asana-gate#readme","keywords":["access-control","agent","asana","gateway","mcp","model-context-protocol","policy"],"repository":{"url":"git+https://github.com/sincekmori/asana-gate.git","type":"git"},"description":"Declarative access-control policy in front of the Asana API, served to AI agents over MCP.","maintainers":[{"name":"sincekmori","email":"sincekmori@gmail.com"}],"readme":"# asana-gate\n\nA declarative access-control policy in front of the [Asana](https://asana.com) REST API, served to AI agents over [MCP](https://modelcontextprotocol.io).\n\n```\nMCP client ──MCP──▶ asana-gate ──policy──▶ Asana REST API\n```\n\nYou give an agent a Personal Access Token through asana-gate instead of directly.\nA policy file then decides, per project, section, task, tag or assignee, what the agent can see and do.\nEverything else does not exist for the agent.\n\n## Why\n\nAn Asana token grants everything its owner can do.\nAgents need much less: read this team, update tasks in that project, never touch the Done section, never delete.\nasana-gate turns such sentences into a YAML file and enforces it on every one of Asana's REST operations.\n\n- **The policy is the only source of permissions.** The token's rights are an upper bound; the default is deny.\n- **Invisible, not forbidden.** Objects the policy hides answer exactly like nonexistent gids (a 404 with Asana's own wording), and never appear in lists, searches, typeahead or events.\n- **Every endpoint is covered.** Every operation of Asana's OpenAPI definition is classified. A plain read, update or delete of one object (`GET /tasks/{task_gid}`) is classified from its path; any other operation Asana adds fails the build until it is classified, and the weekly OpenAPI report names every new one for review, so none passes through unreviewed.\n- **MCP as specified.** stdio and Streamable HTTP transports, no client-specific extensions.\n\n## Install\n\n```sh\nnpm install -g asana-gate\n```\n\nNode.js 24 or later is required.\n`npx asana-gate` works too.\nThe server is listed in the [MCP Registry](https://registry.modelcontextprotocol.io) as `io.github.sincekmori/asana-gate`, for the clients and catalogs that read it.\n\n## Quick start\n\n1. Create a [Personal Access Token](https://developers.asana.com/docs/personal-access-token) and give it to asana-gate: exported for this shell, or saved in your home directory in a file only you can read (it is never printed).\n\n   ```sh\n   export ASANA_ACCESS_TOKEN=\"…\"   # this shell only\n   asana-gate token set --user     # or keep it in ~/.asana-gate/token, typed unseen or piped in\n   ```\n\n2. Let asana-gate look at your workspace and create the project's `.asana-gate` directory: a policy skeleton, a settings file and a `.gitignore` that keeps personal settings and the token file out of git.\n\n   ```sh\n   asana-gate init\n   ```\n\n3. Edit `.asana-gate/policy.yaml`, then validate it: names are resolved against Asana, every gid the rules name is checked to exist, and the token is checked.\n\n   ```sh\n   asana-gate check\n   ```\n\n4. Serve it to your MCP client.\n\n   ```sh\n   asana-gate mcp\n   ```\n\n   For Claude Code, `asana-gate init --agent claude-code` writes the project's `.mcp.json`, a copy of the skill and a permission rule that keeps the token from the agent (see [Agents](#agents)).\n   For any other MCP host, register the command; started inside the project directory, `asana-gate mcp` finds the policy and the token by itself, and `-C` points it at the project when the host starts it elsewhere:\n\n   ```json\n   {\n     \"mcpServers\": {\n       \"asana-gate\": {\n         \"command\": \"npx\",\n         \"args\": [\"-y\", \"asana-gate\", \"mcp\", \"-C\", \"/path/to/project\"]\n       }\n     }\n   }\n   ```\n\n## Policy\n\nA policy names one workspace and lists rules.\nEach rule has a scope (`where`), the actions it allows or denies there, and optionally constraints on the requests made there.\n\n```yaml\nversion: 1\nworkspace: \"1200000000000001\" # a gid or a name\n\nrules:\n  # No `where`: the whole workspace. Read everything.\n  - allow: [read]\n\n  # Everything a team owns is writable (create and update, no delete).\n  - where: { team: \"Platform\" }\n    allow: [write]\n\n  # Full task work in one project, plus comments and tags.\n  - where: { project: \"1200000000000123\" }\n    allow: [\"task:*\", story:create, tag:apply]\n\n  # ...but its Done section is frozen (still visible; deny: [\"*\"] would hide it).\n  - where: { project: \"1200000000000123\", section: \"Done\" }\n    deny: [modify]\n\n  # Tasks tagged ai-ok may be updated wherever they are already visible.\n  - where: { tag: \"ai-ok\" }\n    allow: [task:update]\n\n  # Read a project, and update only these task fields in it.\n  - where: { project: \"Design System\" }\n    allow: [read]\n    fields: { task: [completed, assignee, due_on] }\n\n  # Tasks created here get a prefix and a tag, must have a due date,\n  # are capped at 20 an hour, and are deleted only after a person confirms.\n  - where: { project: \"AI backlog\" }\n    allow: [\"task:*\"]\n    require: { task: { due_on: true } }\n    apply: { task: { name: { prefix: \"[AI] \" }, tags: { add: [ai-generated] } } }\n    limit: { \"task:create\": { max: 20, per: 1h } }\n    confirm: [task:delete]\n\n  # Hide a project completely.\n  - where: { project: \"Payroll\" }\n    deny: [\"*\"]\n```\n\nNames are resolved to gids when the policy loads; an unknown or ambiguous name is an error.\nGids always work.\nEvery scope key accepts one value or a list (any of them matches).\n\n### Scopes\n\n| Key              | Matches                                                                                  | Level |\n| ---------------- | ---------------------------------------------------------------------------------------- | ----- |\n| _(none)_         | the whole workspace                                                                      | 0     |\n| `team`           | the team and every project in it                                                         | 1     |\n| `portfolio`      | the portfolio, its nested portfolios, and every project in them                          | 1     |\n| `unhomed: true`  | tasks that belong to no project (and inherit none from a parent task)                    | 1     |\n| `project`        | the project and everything in it                                                         | 2     |\n| `section`        | a section of the `project` given alongside (a section gid needs no project)              | 3     |\n| `subtree`        | a task (gid) and all of its subtasks, recursively                                        | 4     |\n| `task`           | exactly that task (gid)                                                                  | 5     |\n| `tag`            | filter: tasks carrying the tag                                                           | +     |\n| `assignee`       | filter: tasks assigned to `me`, a gid or an email                                        | +     |\n| `custom_field`   | filter: tasks whose field (by name or gid) holds one of the values, e.g. `{ Owner: AI }` | +     |\n| `created_by`     | filter: tasks created by `me`, a gid or an email                                         | +     |\n| `completed`      | filter: completed (`true`) or open (`false`) tasks                                       | +     |\n| `has_parent`     | filter: subtasks (`true`) or top-level tasks (`false`)                                   | +     |\n| `name`           | filter: tasks whose name satisfies `prefix`, `suffix`, `contains` or `matches` (a regex) | +     |\n| `overdue`        | filter: tasks whose due date has passed (`true`) or not (`false`)                        | +     |\n| `due_within`     | filter: tasks due within a duration from now, such as `7d`                               | +     |\n| `created_within` | filter: tasks created within a duration, such as `24h`                                   | +     |\n\nHierarchy keys in one `where` are ANDed.\nFilters (`tag`, `assignee`, `custom_field` and the state filters below them) are ANDed with the hierarchy keys and never make an object visible on their own: they narrow or widen what may be done with objects that another rule already lets the agent read, and they may hide objects (`deny: [task:read]`).\nFor a create request, the filters see the object the request would create: its name after `apply`, the token's user as its creator, its due date and so on.\n\nObjects that are not tasks live at the nearest hierarchy level: stories, attachments, time entries and the like follow their task; sections, briefs, status updates, memberships, templates and webhooks follow their project, portfolio or goal; tags, users, custom field definitions and most administrative resources live at workspace level.\n\n### Actions\n\nAn action is `<resource>:<verb>`.\nGroups and wildcards expand to concrete actions: `read` (every `read`), `modify` (every other verb, the complement of `read`), `write` (`read` plus every creating and modifying verb), `admin` (everything), `*` (same as `admin`), `task:*`, `*:delete`.\nA rule takes part only for the actions it names, so a scope is made read-only with `allow: [read]` and `deny: [modify]` together: the deny keeps a broader `allow` elsewhere from reaching it, and unlike `deny: [\"*\"]` it leaves the objects visible.\n\n| Resource                                                                                                                                                                                         | Verbs                                                                                                    |\n| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- |\n| `task`                                                                                                                                                                                           | `read` `create` `update` `delete` `complete` `move` `add_project` `remove_project` `set_parent` `assign` |\n| `story` `project_brief` `goal` `goal_relationship` `membership`                                                                                                                                  | `read` `create` `update` `delete`                                                                        |\n| `attachment`                                                                                                                                                                                     | `read` `create` `delete`                                                                                 |\n| `section`                                                                                                                                                                                        | `read` `create` `update` `delete` `reorder`                                                              |\n| `project`                                                                                                                                                                                        | `read` `create` `update` `delete` `archive` `manage_members`                                             |\n| `portfolio`                                                                                                                                                                                      | `read` `create` `update` `delete` `manage_members`                                                       |\n| `status_update`                                                                                                                                                                                  | `read` `create` `delete`                                                                                 |\n| `tag`                                                                                                                                                                                            | `read` `create` `update` `delete` `apply`                                                                |\n| `custom_field` `allocation` `budget` `rate` `role` `record` `table` `ooo_entry` `time_tracking_category` `time_tracking_entry`                                                                   | `read` `create` `update` `delete`                                                                        |\n| `custom_field_setting`                                                                                                                                                                           | `read` `create` `delete`                                                                                 |\n| `project_template`                                                                                                                                                                               | `read` `create` `delete`                                                                                 |\n| `task_template`                                                                                                                                                                                  | `read` `delete`                                                                                          |\n| `team`                                                                                                                                                                                           | `read` `create` `update` `manage_members`                                                                |\n| `workspace`                                                                                                                                                                                      | `read` `update` `manage_members`                                                                         |\n| `user` `notification` `project_portfolio_setting`                                                                                                                                                | `read` `update`                                                                                          |\n| `access_request` `timesheet_approval_status`                                                                                                                                                     | `read` `create` `update`                                                                                 |\n| `webhook`                                                                                                                                                                                        | `read` `create` `update` `delete`                                                                        |\n| `organization_export`                                                                                                                                                                            | `read` `create`                                                                                          |\n| `export`                                                                                                                                                                                         | `create`                                                                                                 |\n| `rule`                                                                                                                                                                                           | `trigger`                                                                                                |\n| `project_membership` `portfolio_membership` `team_membership` `workspace_membership` `user_task_list` `custom_type` `job` `event` `audit_log` `ai_studio_usage` `agent` `time_period` `reaction` | `read`                                                                                                   |\n\n`read` is the prerequisite of every other verb: an object whose `read` is not allowed is invisible, whatever else a rule says.\n\nSome verbs are implied by the request body: updating a task's `completed` needs `task:complete`, and so does the `approval_status` of an approval task, which Asana keeps in step with it (a new approval task in a status other than pending counts as completed, too); its `assignee` needs `task:assign`, a project's `archived` needs `project:archive`, a section's `insert_before` or `insert_after` needs `section:reorder`; every other member needs `update`.\nA custom field defined in place where one is put on a project, a portfolio, a goal or a table is created by that request, so it needs `custom_field:create` in the workspace as well, and the constraints on `custom_field` shape the definition.\nOne named by gid must be visible to the policy, like any object a request names, to be put on and to be taken off.\n\n**Explicit-only actions** move data out of Asana or out of asana-gate's control, so no group or wildcard grants them; a policy must spell them out: `webhook:create`, `webhook:update`, `export:create`, `organization_export:create`, `organization_export:read`, `audit_log:read`.\nAsana restricts some operations further on its own side, and the gate passes its answer through: audit log events, workspace events, organization exports and graph exports are served only to a service account of an Enterprise-tier organization, task templates, allocations, rates and custom roles take a paid tier, and the early-access Agents endpoints answer only requests that carry the `ai_teammate_actors` flag, which `asana.enable` in the [settings](#configuration) sends.\nWhere a policy restricts rather than grants (`deny`, `confirm`, `limit`), groups and wildcards do cover them, so `deny: [modify]` also refuses `webhook:create` there.\n\n### `fields`\n\n`fields` on a rule grants `<resource>:update` limited to the listed members (plus the verb a member stands for, such as `task:complete` for `completed`).\nAn update that touches any other member is refused with a 403 naming the member.\nA task's `dependencies` and `dependents`, which their own operations change (`addDependencies`, `removeDependents`, …), may be listed too.\nIt applies to updates only; creating an object is governed by `create` alone.\n\n### Constraints\n\nBesides allowing and denying actions, a rule can constrain the requests made in its scope and the responses they get: what a member must look like, what is filled in, what may not be set, what is hidden, how often an action may run and what a person must confirm.\nA rule may consist of constraints alone, without `allow` or `deny`; its `where` decides where they are in force.\n\n```yaml\nrules:\n  - where: { project: \"AI backlog\" }\n    allow: [\"task:*\", story:create]\n    require:\n      task:\n        name: { prefix: \"[AI] \", max_length: 80 }\n        due_on: { present: true, min: today, max: \"+30d\" }\n        custom_fields: { Owner: { in: [AI] } }\n    apply:\n      task:\n        name: { prefix: \"[AI] \" }\n        tags: { add: [ai-generated] }\n        custom_fields: { Owner: AI }\n    forbid: { task: [html_notes, followers] }\n    redact: { task: [notes] }\n    limit: { \"task:create\": { max: 20, per: 1h } }\n    confirm: [task:delete, \"project:*\"]\n```\n\n| Clause    | Acts on                    | Meaning                                                                                                                  |\n| --------- | -------------------------- | ------------------------------------------------------------------------------------------------------------------------ |\n| `require` | create and update requests | per resource and member, what the value must satisfy; a request that does not is refused with a 400 naming every problem |\n| `apply`   | create and update requests | per resource and member, what is filled in or rewritten before the request reaches Asana                                 |\n| `forbid`  | create and update requests | per resource, members the request may not set                                                                            |\n| `redact`  | responses                  | per resource, members removed from every object the agent sees                                                           |\n| `limit`   | actions                    | per action, at most `max` requests per `per` (`30m`, `24h`, `7d`); the next one is refused with a 429                    |\n| `confirm` | actions                    | actions a person must confirm before they run: 428 when nobody can be asked, 403 when they decline                       |\n\nMembers are the request members of Asana's API (`name`, `due_on`, `assignee`, `projects`, `tags`, …); a member Asana does not accept for the resource is an error when the policy loads.\n`custom_fields` nests by field name or gid, and the values of an enum field may be option names or gids; a field named like an operator (`in`, `value`, …) is named by its gid, and operators may not stand beside field names.\nNames in `in`, `not_in` and `apply` values are resolved when the policy loads, like names in `where`: enum option names, tag names (`tags`), users (`me` or an email for `assignee`, `followers`, `owner`), projects and teams; a request may then send either the gid or the name, and `apply` sends the gid.\n\nA requirement combines operators, all of which must hold:\n\n| Operator                         | Meaning                                                                                                                                                                                              |\n| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `present: true` (or just `true`) | required when creating; cannot be cleared when updating                                                                                                                                              |\n| `prefix`, `suffix`, `contains`   | the string must start with, end with or contain the text                                                                                                                                             |\n| `matches`, `not_matches`         | the string must, or must not, match the regular expression                                                                                                                                           |\n| `min_length`, `max_length`       | bounds on the string's length                                                                                                                                                                        |\n| `in`, `not_in`                   | the value, or every element of a list, must (not) be one of these; references compare by gid or name                                                                                                 |\n| `min`, `max`                     | bounds on a number, or on a date: `YYYY-MM-DD`, ISO 8601, `today`, `now`, `+7d`, `-1d` (a date-only value such as `due_on` is compared by calendar day, and a time without an offset is read as UTC) |\n\nAn application is a bare value (a default) or an object of operators:\n\n| Operator           | Meaning                                                                             |\n| ------------------ | ----------------------------------------------------------------------------------- |\n| `default`          | set when the member is absent or empty (on update, only when the request clears it) |\n| `value`            | always set, whatever the request says                                               |\n| `prefix`, `suffix` | added to the string unless already there                                            |\n| `add`              | values a list member must contain                                                   |\n\nWhen several rules apply to one object, every `require` holds, the most specific rule's `apply` wins per member, and `forbid`, `redact` and `confirm` add up.\nA request is shaped in the order `apply`, `forbid`, `require`, so a default or a prefix can satisfy a requirement.\nLimits count per rule and action inside one gate process, over a sliding window, and a refused request does not count; they are a brake on runaway agents, not an audit trail.\n\n### How a request is decided\n\n1. The request is matched to one of Asana's operations, and the objects it touches are loaded from Asana to find their place: workspace, team, portfolios, project, section, parent tasks, tags, assignee, custom field values.\n2. For each action the operation needs, the most specific matching rules decide.\n   Specificity is the hierarchy level of the scope (see the table), then the number of filters; between rules of equal specificity, `deny` wins.\n   A rule that mentions neither the action nor the scope does not take part.\n   No matching rule means deny.\n3. A task multi-homed in several projects must be allowed in every one of them; if any of its projects hides it, the task is invisible.\n4. A subtask with no project of its own takes its placement from the nearest ancestor that has one (up to five levels); failing that it is unhomed.\n5. Invisible objects answer with Asana's \"Not a recognized ID\" 404.\n   Visible objects on which the action is not allowed answer with a 403 whose message starts with `asana-gate:`.\n6. A create or update request is then shaped by the constraints in force: `apply` completes it, and a member that breaks `forbid` or `require` refuses it with a 400 naming every problem.\n7. A `limit` that is already full refuses with a 429; an action under `confirm` runs only after a person confirms (428 when nobody can be asked, 403 when they decline).\n   The order matters: a later refusal never reveals what an earlier one hides, nobody is asked to confirm a request that would be refused anyway, and a refused request does not count against a limit.\n8. Lists, searches, typeahead and events are filtered; nothing says how many items were removed (`GET /projects/{gid}/task_counts` is the exception: it is passed through and counts the project's hidden tasks too).\n   A filtered page is refilled from the following pages so that it stays as full as asked for, never fuller.\n   A `limit` or `confirm` on a read action applies to lists of that resource as well, once per request.\n9. Every object in a response carries `allowed_actions`, the actions the policy currently allows on it, so an agent can plan before acting; members under `redact` are removed.\n   Nested references to hidden objects (a subtask's `parent`, `dependencies`, a job's `new_task`, …) are removed, and visible ones are redacted as their own place in the policy says.\n\nRule order in the file does not matter.\n`asana-gate explain <gid>` shows how the policy treats one object, which rules decided each action, and the constraints in force on it.\n\n### Several policies\n\nThe policy in force is made of up to three files: the project's `.asana-gate/policy.yaml` (or the file `--policy` points at), your own `~/.asana-gate/policy.yaml`, and an administrator's `managed-policy.yaml` beside the managed settings.\nEvery one of them that exists is read, and an action is allowed only when every file allows it: each file is evaluated on its own, with its own most specific rule deciding and its own default of deny, and the answers are combined with AND.\nSo your own policy is the most you can ever do in any project, the administrator's the most anyone on the machine can do, and the project's what this project allows within those bounds; a file that does not mention an action denies it, exactly as a lone policy would.\nWith `allow: [read]` in one file and `allow: [task:read]` in another, only tasks can be read, whichever file says which; with `allow: [team:read]` in one and `allow: [task:read]` in the other, nothing can.\nConstraints add up across files the way matching rules of one file do, `fields` allowlists intersect, and where two files `apply` the same member at equal specificity the stronger wins: the administrator's, then the project's, then yours.\nA file other than the project's may leave `workspace` out, and is then in force wherever the project's policy is; one that names another workspace is not in force there, which `check` reports.\nWhen the project has no policy, yours is the policy, bounded by the administrator's; when only the administrator's exists, it is the policy.\n`check` lists every file in force, and messages name a rule by its file when there are several (`user rules[2]`).\n\n## MCP server\n\n`asana-gate mcp` serves the curated tools the policy could ever allow (a read-only policy lists no writing tool), plus three generic ones; the policy is applied when a tool runs.\nClaude Code loads tool definitions on demand once they grow large, so a long list costs little there.\nThe server's instructions tell the agent whom every request runs as: the gid of the token's user and the name and gid of the workspace, so it can tell which `assignee`, `created_by` or `followers` in a response is itself; the user's name and email are added only as far as the policy would show them through `GET /users/me` (`workspace:read` and `user:read` at workspace level, then `redact`).\n\n- Curated tools for everyday work: `asana_search_tasks`, `asana_list_tasks`, `asana_get_task`, `asana_create_task`, `asana_update_task`, `asana_create_comment`, `asana_move_task_to_section`, `asana_add_tag_to_task`, `asana_list_projects`, `asana_create_section`, `asana_typeahead`, `asana_get_me` and more.\n- `asana_create_tasks` and `asana_update_tasks` take up to 50 tasks at once, `asana_create_records` and `asana_update_records` as many records: the gate checks each one, Asana runs them ten at a time, and the result holds one status per task or record.\n- `asana_get_task` answers the task's latest comments and its direct subtasks in the same call when asked (`include_comments`, `include_subtasks`), and `asana_get_project` its sections and task counts (`include_sections`, `include_task_counts`): each part is a request of its own to the gate, and one the policy or Asana refuses is `null`.\n- `asana_request` calls any REST operation (`method`, `path`, `query`, `body`) through the same policy; a `POST /batch` through it takes up to 50 actions.\n- `asana_operations` lists the operations with the action each one needs; `asana_allowed_actions` tells what the policy allows on one object.\n\nRefusals come back as tool errors whose text is the JSON error body, so agents see the same wording a direct API client would.\nA tool refuses an argument its input does not declare, naming it, rather than run without it; `asana_request` takes every member of an operation.\n\n### Confirmations\n\nWhen a rule's `confirm` covers the action, the server asks the person through MCP elicitation before the call runs; nothing reaches Asana until they say yes.\nOn a connection that negotiated the 2026-07-28 protocol revision the tool call answers with an `input_required` result carrying a form elicitation and a sealed `requestState`; the client shows it and resends the same call with the answer and the state, which the server checks before executing, so an answer counts only for the question this server asked, about the call with these very arguments.\nOn an older connection the server sends `elicitation/create` itself and waits up to ten minutes for the answer.\nA declined or cancelled confirmation refuses the call with a 403.\nA client that does not implement elicitation cannot confirm, so the action does not run (428).\nOver the HTTP transport an older client is served one request at a time and cannot receive `elicitation/create`, so confirmations there need a client on the 2026-07-28 revision.\n\n### Transports\n\n```sh\nasana-gate mcp                         # stdio (default)\nasana-gate mcp --transport http        # Streamable HTTP on http://127.0.0.1:3845/mcp\nasana-gate mcp --transport http --host 0.0.0.0 --port 8080 --allowed-host gate.example.internal\n```\n\nThe HTTP transport validates `Host` and `Origin` headers against loopback plus `--allowed-host` entries (DNS rebinding protection).\nBinding to anything but loopback requires a bearer token in `ASANA_GATE_MCP_TOKEN` (or the variable named by `--auth-token-env`), which clients must send as `Authorization: Bearer …`.\n\n## CLI\n\n```\nasana-gate mcp                     Serve the policy-gated Asana API as an MCP server\nasana-gate check                   Validate the settings, the token and the policy against Asana\nasana-gate explain <gid>           Show what the policy allows on one object, and why\nasana-gate init                    Create the project's .asana-gate directory; --agent claude-code wires Claude Code\nasana-gate token                   Show where the Asana token comes from, or save one (never printed)\nasana-gate settings                Show the settings in force and where each value comes from\nasana-gate cache                   Show or clear the on-disk cache of workspace names\nasana-gate <resource> <verb> …     Operate Asana through the policy\nasana-gate api <METHOD> <path>     Call any Asana REST operation through the policy\n```\n\nCommon options: `-C <dir>` (run as if started in `<dir>`), `--policy <file>` on the commands that read a policy (default: the project's `.asana-gate/policy.yaml`, see [Configuration](#configuration)), `--token-env <NAME>` (default `ASANA_ACCESS_TOKEN`), `--log-level silent|error|warn|info|debug`.\n`check` fails (exit code 1) on a problem, such as an object the policy names that no longer exists, and only warns about the rest.\n`init` and `explain` read Asana without the policy's restrictions; they exist to write policies and are not reachable over MCP.\n`explain` also prints the constraints in force on the object.\n\n### Operating Asana from a shell\n\nEvery curated MCP tool is also a `<resource> <verb>` command with the same inputs, so whatever an agent may do over MCP, a person may do from a shell under the same policy.\n\n```sh\nasana-gate task list --project 1200000000000123 --completed-since now\nasana-gate task create --name \"Write docs\" --projects 1200000000000123 --due-on 2026-12-01\nasana-gate task update 1200000000000456 --assignee me --completed\nasana-gate task move 1200000000000456 --section 1200000000000789\nasana-gate task comment 1200000000000456 --text \"Done, see the attached diff.\"\nasana-gate task delete 1200000000000456\nasana-gate task create-many --tasks @tasks.json\nasana-gate section create --project 1200000000000123 --name \"Review\"\nasana-gate find design --type project\nasana-gate api GET /tasks/1200000000000456 -q opt_fields=name,completed\nasana-gate api POST /tasks -d '{\"name\": \"Write docs\", \"projects\": [\"1200000000000123\"]}'\n```\n\n- The object a verb acts on is a positional argument; everything else is a flag named after the API member (`--due-on` for `due_on`).\n- Booleans are switches (`--completed`, `--no-completed`); lists take comma-separated values or repeated flags; `--custom-fields`, `--tasks` and other objects take JSON, inline, from a file (`@tasks.json`, relative to `-C`) or from standard input (`-`); `null` clears a member that allows it.\n- Lists print as tables with a hint for the next page, objects as `key: value` lines; `--json` prints the response body as Asana returns it, which `api` always does.\n- When the policy wants an action confirmed, the command asks on the terminal; `--yes` (`-y`) confirms in scripts, and a non-interactive run without it is refused.\n- Exit codes: 0 on success, 1 when Asana or the policy refuses the request, 2 for a usage error.\n- A `limit` counts inside one process, so it binds the MCP server; one-shot commands start from zero each time.\n- `asana-gate <resource> --help` lists the verbs; `asana-gate <resource> <verb> --help` lists the flags, with what is required and what the choices are.\n\nLogs go to stderr and, by default, to `~/.asana-gate/logs/asana-gate.log` (`log.file` in the [settings](#configuration)).\nThe token is never written to logs, errors, URLs or responses.\nAt `info` level the client also reports the API changes Asana announces in its `Asana-Change` response header.\n\n## Configuration\n\nasana-gate keeps its files the way Claude Code does: a `.asana-gate` directory in the project, one in your home directory, and settings an administrator can manage.\n\n| Layer                 | Where                                                                                                                                                                                                                                                                                                  | For                                       |\n| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------- |\n| Managed               | `/Library/Application Support/asana-gate/managed-settings.yaml` (macOS), `/etc/asana-gate/managed-settings.yaml` (Linux), `%ProgramData%\\asana-gate\\managed-settings.yaml` (Windows), plus `managed-settings.d/*.yaml`; `managed-policy.yaml` beside them is a policy every other policy is bounded by | An administrator; nothing overrides these |\n| Flags and environment | `-C`, `--policy`, `--token-env`, `--log-level`; `ASANA_GATE_POLICY`, `ASANA_GATE_LOG_LEVEL`, `ASANA_GATE_CACHE=off`, `ASANA_GATE_HOME`                                                                                                                                                                 | One invocation                            |\n| Project, personal     | `.asana-gate/settings.local.yaml`                                                                                                                                                                                                                                                                      | You, in this project (ignored by git)     |\n| Project, shared       | `.asana-gate/settings.yaml`                                                                                                                                                                                                                                                                            | Everyone working in the project           |\n| User                  | `~/.asana-gate/settings.yaml`                                                                                                                                                                                                                                                                          | You, in every project                     |\n\nHigher rows win.\nThe project is the nearest directory, from the working directory upwards, that holds `.asana-gate`; `asana-gate init` creates it, and `asana-gate init --user` sets up `~/.asana-gate` instead.\n`ASANA_GATE_HOME` moves the home directory.\n`asana-gate settings` prints the settings in force and the file each value came from.\n\nEvery layer may set any of these members, all optional; relative paths are relative to the file that names them.\n\n| Member                                                                          | Default                                                                                                                                     | Meaning                                                                                                                                                                                                                                               |\n| ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `policy`                                                                        | the project's `.asana-gate/policy.yaml`, else `./asana-gate.yaml`, else `~/.asana-gate/policy.yaml`, else the managed `managed-policy.yaml` | The project's policy file; `~/.asana-gate/policy.yaml` and `managed-policy.yaml`, when they exist, bound it: every file must allow an action (see [Several policies](#several-policies))                                                              |\n| `token.env`                                                                     | `ASANA_ACCESS_TOKEN`                                                                                                                        | The environment variable holding the Personal Access Token (the name Asana's own client libraries use)                                                                                                                                                |\n| `token.command`                                                                 | –                                                                                                                                           | A command whose output is the token, such as `op read \"op://Private/Asana/credential\"`; honored from user and managed settings only                                                                                                                   |\n| `token.file`                                                                    | the project's `.asana-gate/token`, else `~/.asana-gate/token`                                                                               | A file holding the token on its first line                                                                                                                                                                                                            |\n| `log.level`                                                                     | `warn`                                                                                                                                      | `silent`, `error`, `warn`, `info` or `debug`                                                                                                                                                                                                          |\n| `log.file`                                                                      | `~/.asana-gate/logs/asana-gate.log`                                                                                                         | A file log lines are also appended to, created readable by you alone (`check` warns if not), rotated at 10 MB; `null` for none                                                                                                                        |\n| `cache.enabled`                                                                 | `true`                                                                                                                                      | Whether name resolution keeps the workspace's structure on disk between runs                                                                                                                                                                          |\n| `cache.dir`                                                                     | `~/.asana-gate/cache`                                                                                                                       | Where; one subdirectory per token, named by a hash of it                                                                                                                                                                                              |\n| `cache.ttl`                                                                     | `7d`                                                                                                                                        | How long a cached listing is trusted                                                                                                                                                                                                                  |\n| `concurrency.reads`                                                             | `50`                                                                                                                                        | Concurrent GET requests to Asana (its limit)                                                                                                                                                                                                          |\n| `concurrency.writes`                                                            | `15`                                                                                                                                        | Concurrent POST, PUT and DELETE requests (its limit)                                                                                                                                                                                                  |\n| `retries.max`                                                                   | `5`                                                                                                                                         | Retries after a 429, or after a 5xx for anything but a POST, waiting as long as `Retry-After` says                                                                                                                                                    |\n| `retries.maxWait`                                                               | `60s`                                                                                                                                       | The longest wait before a retry; a longer `Retry-After` is cut to it                                                                                                                                                                                  |\n| `asana.enable`                                                                  | `[]`                                                                                                                                        | Flags sent in the `Asana-Enable` header of every request: `ai_teammate_actors` opts in to the early-access Agents endpoints, and an announced change's flag takes it before its date (see [Keeping up with Asana's API](#keeping-up-with-asanas-api)) |\n| `asana.disable`                                                                 | `[]`                                                                                                                                        | Flags sent in the `Asana-Disable` header: an announced change kept off while Asana still allows it                                                                                                                                                    |\n| `mcp.transport`, `mcp.host`, `mcp.port`, `mcp.allowedHosts`, `mcp.authTokenEnv` | `stdio`, `127.0.0.1`, `3845`, `[]`, `ASANA_GATE_MCP_TOKEN`                                                                                  | The defaults of `asana-gate mcp`                                                                                                                                                                                                                      |\n\nA JSON Schema ships as `asana-gate/settings.schema.json`; `init` writes a `# yaml-language-server: $schema=…` pointer so editors validate the file.\nProject settings are trusted like the project's code, which is why `token.command` is not honored from them.\n\n### The token\n\nThe Personal Access Token is read from the first of these sources, and `asana-gate token status` says which one is in use (the token itself is never printed):\n\n1. the environment variable named by `token.env` (`ASANA_ACCESS_TOKEN`);\n2. the `token.command` of your own or managed settings;\n3. the file named by `token.file`, else the project's `.asana-gate/token`, else `~/.asana-gate/token`.\n\n`asana-gate token set` saves a token, typed unseen or piped in, to the file read first (`token.file` when set, else the project's `.asana-gate/token`) and lists that file in `.asana-gate/.gitignore` when it is inside `.asana-gate`; `asana-gate token set --user` saves it to `~/.asana-gate/token`.\nThe files are created readable by you alone, and `check` warns when one is not.\nA token file in the project is what hosts without environment variables read, such as Claude Cowork (see [Agents](#agents)).\n\n### Cache\n\nResolving the names in a policy (teams, projects, sections, tags, custom fields) means listing them, and that is the slow part of starting the gate.\nWith the cache on, those listings are kept under `cache.dir` in files only you can read and reused until `cache.ttl` passes; a name missing from a cached listing is looked up live before it counts as unknown, so a project created an hour ago still resolves.\nThe cache holds the names and gids of the workspace's structure, never tokens, tasks or comments; what the gate learns about objects while it runs stays in memory.\nWhere even that is too much, turn it off in any layer with `cache.enabled: false`, for one run with `ASANA_GATE_CACHE=off`, or for everyone with a managed setting.\n`asana-gate cache` shows the cache and `asana-gate cache clear` deletes every token's listings in it (other files in `cache.dir` stay).\n\n### Concurrency\n\nThe gate sends independent requests at the same time, up to Asana's own limits of 50 reads and 15 writes in flight per token (lower if `concurrency` says so): a page of tasks is checked with one lookup per task at once, the objects a write names are loaded together, and the actions of a `POST /batch` are planned together.\nWhen Asana answers 429, the request waits the seconds its `Retry-After` header names (cut to `retries.maxWait`) and tries again, up to `retries.max` times, so running at the limit costs nothing but the wait; a 5xx is retried the same way after 1, 2, 4… seconds, or longer when its `Retry-After` asks, unless the request is a POST: Asana may have run it before failing, and a POST sent twice can create or add twice, so its 5xx is returned as it is.\nAn agent that needs many objects at once should send one `POST /batch` with up to ten actions rather than ten calls; the gate checks each action and Asana runs them as one request.\n\n### Noticing failures\n\nThe gate degrades rather than stops when its own files fail: a cache directory that cannot be written is left alone after one warning and names are read from Asana each time, and a log file that cannot be opened leaves warnings on stderr only.\nThree things make such a failure visible:\n\n- the warning itself, on stderr and in the log file (`~/.asana-gate/logs/asana-gate.log` by default), where the MCP server's warnings land even when nobody watches its stderr;\n- `asana-gate check`, which probes the cache and log directories, the token file's permissions and every object the policy names, and fails on what is broken;\n- `asana-gate cache`, which shows whether the cache directory is writable.\n\n## Keeping up with Asana's API\n\nThe repository holds structural snapshots of Asana's public OpenAPI definition: every operation with its parameters and body members ([`src/catalog/operations.gen.ts`](src/catalog/operations.gen.ts)) and every response schema as property names ([`src/catalog/schemas.gen.ts`](src/catalog/schemas.gen.ts)).\nWording is deliberately left out, so the snapshots change only when the API changes.\n\nA weekly workflow refreshes them and opens a pull request whose description, produced by `scripts/openapi-report.ts`, lists the added, removed, changed and deprecated operations, the changed response fields, and what asana-gate must do about them.\nCI fails on that pull request until every new operation is classified and every field the gate reads still exists; a new plain read, update or delete of one object is classified from its path, and the report lists it with its action to confirm.\n\nLocally:\n\n```sh\npnpm sync-openapi && pnpm format && node scripts/openapi-report.ts\n```\n\nThe definition carries no wording, and some of what matters is written only on developers.asana.com: the opt-in flag of an early-access endpoint, a deprecation the definition does not mark, an access restriction.\nA second weekly workflow reads the Markdown source of every page the site's index lists (`llms.txt`, then `<page>.md`) and lists, from the `updatedAt` of their front matter, the pages updated during the week, as a comment on one issue; `pnpm docs-updates` prints the list locally (`--days` widens the window).\n\nAsana itself announces a change with an `Asana-Change` response header, which the gate logs once per change, and rolls it out over a period during which the `Asana-Enable` and `Asana-Disable` request headers choose the behaviour.\nThe `asana.enable` and `asana.disable` settings send those headers on every request, so a change can be taken early or kept off until its end date; `asana.enable` is also where an early-access opt-in goes, such as `ai_teammate_actors` for the Agents endpoints, which Asana refuses without it.\n\n## Agents\n\n### The skill\n\n[`skills/asana-gate`](skills/asana-gate) is an [Agent Skill](https://agentskills.io) that teaches an agent how asana-gate answers, how to work through its tools and commands, and how to write a policy.\nIt is generated from this README and the tool definitions (`pnpm generate-skill`), and a test fails when the committed copy drifts.\n`npx skills add sincekmori/asana-gate` installs it for the agents on your machine; Claude Code also reads the copy that `init --agent claude-code` puts in the project, and Claude Cowork takes it as a zipped upload under Customize > Skills.\n\n### Claude Code\n\n`asana-gate init --agent claude-code` makes a repository use the gate without anyone wiring it by hand:\n\n- `.mcp.json` gains the project-scoped `asana-gate` server (`npx -y asana-gate@<this version> mcp`), which Claude Code asks each person to approve once;\n- `.claude/skills/asana-gate` receives a copy of the skill, which Claude Code loads by itself; `check` warns when the copy is from another version;\n- `.claude/settings.json` gains `Read(./.asana-gate/token)` in `permissions.deny`, so the agent cannot read the token file (Claude Code applies the rule to `cat` and the other file-reading commands as well).\n\nCommit those with the policy, then say in `CLAUDE.md` what the command prints:\n\n```markdown\n## Asana\n\nTasks for this repository live in the Asana project \"<project>\", reached only through asana-gate:\nthe `asana-gate` MCP server in .mcp.json, governed by .asana-gate/policy.yaml.\nRead .claude/skills/asana-gate/SKILL.md before touching Asana.\nNever call the Asana API any other way, and never read .asana-gate/token.\n```\n\nEach person saves their own token with `asana-gate token set` (or exports it), and the policy, reviewed like code, is the whole of what the agent may do.\nThe copy of the skill keeps itself current: whenever `asana-gate mcp` starts in the project with another version than the copy carries, it rewrites the copy, so an upgrade of the pin in `.mcp.json` shows up as a change to commit.\nThe Claude Code extension for VS Code reads the same `.mcp.json`.\n\n### VS Code, Cursor and other agents\n\n`asana-gate init --agent vscode` and `--agent cursor` (repeatable, and combinable with `claude-code`) do the same for those editors: the server goes into `.mcp.json`, which GitHub Copilot in VS Code reads as Claude Code and Copilot CLI do, or into `.cursor/mcp.json`, and the skill into `.agents/skills/asana-gate`, the cross-agent directory that VS Code, Cursor and Codex all read.\nVS Code starts the server without asking once the workspace is trusted; `.vscode/mcp.json`, the file of its deprecated Local agent harness, is not written.\nAn existing file is changed only where the server goes, so its comments stay.\nThe command prints the paragraph for `.github/copilot-instructions.md` or `AGENTS.md`.\nNeither editor can be told to keep its agent from reading a file in the project, so with them keep the token out of it: `asana-gate token set --user`, or the environment variable.\nFor Codex, the skill copy is enough on the file side; register the server with `codex mcp add asana-gate -- npx -y asana-gate@<version> mcp`.\n\n### Hosts without MCP\n\nWhere an MCP server cannot be used, such as Claude Cowork under a policy that disables local servers, the skill works through the command line: every tool is an `asana-gate <resource> <verb>` command with the same inputs under the same policy.\nSuch a host sees only the folder it was given, so keep everything in it: `.asana-gate/policy.yaml` and `settings.yaml` as usual, and the token in `.asana-gate/token`, which `asana-gate token set` writes and `.gitignore` keeps out of git.\nThe commands need Node.js 24 or later and network access to `app.asana.com` (and to the npm registry when they run through `npx`); `asana-gate check` from the folder confirms all of it in one go.\n\n## Notes from live verification\n\nasana-gate was exercised against the real API.\nSome behaviors worth knowing:\n\n- Asana's 404 for a well-formed unknown gid is `task: Not a recognized ID: …`; asana-gate uses the same wording for invisible objects.\n- `POST /tasks` needs `projects`, `parent` or `workspace`; `memberships` alone is rejected, so the `asana_create_task` tool sends `projects` together with `memberships` when a section is given.\n- `POST /sections/{gid}/addTask` adds a task from another project to the section's project; asana-gate therefore requires `task:create` there as well as `task:move`.\n- A task's `parent` cannot be changed through `PUT /tasks/{gid}`; use `setParent`.\n- Batch actions carry query parameters in `data`, not in `relative_path`.\n- The Search API, custom fields, portfolios, goals, task dependencies, milestones, and tables and records are unavailable on free workspaces (402); the gate passes such responses through.\n- `POST /projects/{gid}/removeMembers` refuses `me`, which `addMembers` takes, so `asana_remove_project_members` wants gids.\n- Removing a project's owner from its members leaves the project without an owner, and added back the user is an editor, who can neither take the ownership back nor delete the project.\n- Unknown `opt_fields` are ignored by Asana, so the fields the gate adds to requests never break them.\n- With `opt_fields`, Asana answers the `gid` and the selected members only: a reference selected alone comes back as `{ gid, resource_type }`, and one with a selection inside it (`parent.name`) as `{ gid, name }`, without its `resource_type`. The gate therefore also selects `resource_type` inside every member its fields reach into, to recognize and check nested references, and cuts a `GET` by gid back to the caller's fields before answering.\n- Nested selections reach into referenced objects, including on typeahead results: `memberships.project.team` gives a task's team with the task.\n- Custom fields, custom types, time periods, time tracking categories and out-of-office entries carry no `workspace` member, so the gate places them in the governed workspace; with a token that belongs to several workspaces, rules at workspace level also govern such objects of the other workspaces when an agent names their gids. `PUT /enum_options/{gid}` is checked at workspace level only (Asana offers no way to read an enum option).\n\n## Library\n\nThe package also exports the building blocks for other hosts.\n\n```ts\nimport { AsanaClient, AsanaNameResolver, compilePolicy, Gate, loadPolicyFile } from \"asana-gate\";\n\nconst client = new AsanaClient({ token: process.env.ASANA_ACCESS_TOKEN ?? \"\" });\nconst policy = await compilePolicy(\n  await loadPolicyFile(\"asana-gate.yaml\"),\n  new AsanaNameResolver(client),\n);\nconst gate = new Gate({ client, policy });\n\nconst response = await gate.execute({\n  method: \"GET\",\n  path: \"/projects/1200000000000123/tasks\",\n  query: { limit: \"20\" },\n});\n// response.status, response.body — shaped exactly like Asana's, filtered and decorated with allowed_actions\n```\n\n`loadSettings({ cwd, env })` reads the same layered settings the command line uses.\nJSON Schemas for policy and settings files ship as `asana-gate/schema.json` and `asana-gate/settings.schema.json`; point `\"$schema\"` at them for editor validation.\n\n## Development\n\n```sh\npnpm install\npnpm build          # tsdown (incl. publint + attw)\npnpm test           # vitest\npnpm typecheck      # tsc --noEmit\npnpm lint           # oxlint --type-aware\npnpm format         # oxfmt --write .\npnpm sync-openapi   # refresh the OpenAPI snapshots\npnpm docs-updates   # list the pages of developers.asana.com updated in the last week\npnpm generate-schema # regenerate schema.json and settings.schema.json\npnpm generate-skill  # regenerate the skill from the README and the tool definitions\npnpm generate-server # regenerate server.json, the MCP Registry entry\n```\n\nVersioning and publishing use [Changesets](https://github.com/changesets/changesets): `pnpm changeset` describes a change, and merging to `main` opens a Version Packages PR that publishes to npm when merged.\n\n## License\n\n[Apache-2.0](LICENSE)\n","readmeFilename":""}