Open
Conversation
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
|
|
||
| **Credentials:** `token` | ||
|
|
||
| ### GitLab |
Contributor
There was a problem hiding this comment.
GitLab connector is documented but not implemented in the codebase; remove or mark as coming soon to avoid confusion.
Prompt for AI agents
Address the following comment on docs/connectors.md at line 26:
<comment>GitLab connector is documented but not implemented in the codebase; remove or mark as coming soon to avoid confusion.</comment>
<file context>
@@ -0,0 +1,133 @@
+
+**Credentials:** `token`
+
+### GitLab
+GitLab integration for repository and project management.
+
</file context>
| ### Asana | ||
| Task and project management with Asana. | ||
|
|
||
| **Credentials:** `apiKey` |
Contributor
There was a problem hiding this comment.
HiBob credentials should list serviceUserId and serviceUserToken, not apiKey.
Prompt for AI agents
Address the following comment on docs/connectors.md at line 36:
<comment>HiBob credentials should list serviceUserId and serviceUserToken, not apiKey.</comment>
<file context>
@@ -0,0 +1,133 @@
+### Asana
+Task and project management with Asana.
+
+**Credentials:** `apiKey`
+
+### Jira
</file context>
Suggested change
| **Credentials:** `apiKey` | |
| **Credentials:** `serviceUserId`, `serviceUserToken` |
| ### Supabase | ||
| Backend-as-a-service with database, auth, and storage. | ||
|
|
||
| **Credentials:** `url`, `anonKey` |
Contributor
There was a problem hiding this comment.
Supabase credentials are incorrect; use accessToken to match the connector config.
Prompt for AI agents
Address the following comment on docs/connectors.md at line 77:
<comment>Supabase credentials are incorrect; use accessToken to match the connector config.</comment>
<file context>
@@ -0,0 +1,133 @@
+### Supabase
+Backend-as-a-service with database, auth, and storage.
+
+**Credentials:** `url`, `anonKey`
+
+## Analytics & Monitoring
</file context>
| ### Asana | ||
| Task and project management with Asana. | ||
|
|
||
| **Credentials:** `apiKey` |
Contributor
There was a problem hiding this comment.
Notion credential key should be token, not apiKey, per the connector schema.
Prompt for AI agents
Address the following comment on docs/connectors.md at line 36:
<comment>Notion credential key should be token, not apiKey, per the connector schema.</comment>
<file context>
@@ -0,0 +1,133 @@
+### Asana
+Task and project management with Asana.
+
+**Credentials:** `apiKey`
+
+### Jira
</file context>
Suggested change
| **Credentials:** `apiKey` | |
| **Credentials:** `token` |
| ### Slack | ||
| Team communication and workflow automation. | ||
|
|
||
| **Credentials:** `botToken` |
Contributor
There was a problem hiding this comment.
Slack requires teamId in addition to botToken; document both to prevent misconfiguration.
Prompt for AI agents
Address the following comment on docs/connectors.md at line 58:
<comment>Slack requires teamId in addition to botToken; document both to prevent misconfiguration.</comment>
<file context>
@@ -0,0 +1,133 @@
+### Slack
+Team communication and workflow automation.
+
+**Credentials:** `botToken`
+
+## Documentation & Knowledge
</file context>
Suggested change
| **Credentials:** `botToken` | |
| **Credentials:** `botToken`, `teamId` |
|
|
||
| console.log( | ||
| '[get_available_hstacks_images] Creating client with token:', | ||
| `${accessToken.substring(0, 8)}...` |
Contributor
There was a problem hiding this comment.
Partial access token is logged; mask or remove token output entirely.
Prompt for AI agents
Address the following comment on packages/mcp-connectors/src/connectors/hstacks.ts at line 207:
<comment>Partial access token is logged; mask or remove token output entirely.</comment>
<file context>
@@ -0,0 +1,396 @@
+
+ console.log(
+ '[get_available_hstacks_images] Creating client with token:',
+ `${accessToken.substring(0, 8)}...`
+ );
+ const client = new HStacksClient(accessToken);
</file context>
| try { | ||
| console.log('[get_available_hstacks_images] Starting'); | ||
| const credentials = await context.getCredentials(); | ||
| console.log('[get_available_hstacks_images] Credentials:', credentials); |
Contributor
There was a problem hiding this comment.
Full credentials object (including access token) is logged; avoid printing secrets.
Prompt for AI agents
Address the following comment on packages/mcp-connectors/src/connectors/hstacks.ts at line 198:
<comment>Full credentials object (including access token) is logged; avoid printing secrets.</comment>
<file context>
@@ -0,0 +1,396 @@
+ try {
+ console.log('[get_available_hstacks_images] Starting');
+ const credentials = await context.getCredentials();
+ console.log('[get_available_hstacks_images] Credentials:', credentials);
+ const { accessToken } = credentials;
+
</file context>
Suggested change
| console.log('[get_available_hstacks_images] Credentials:', credentials); | |
| console.log('[get_available_hstacks_images] Credentials: [REDACTED]'); |
| } | ||
|
|
||
| try { | ||
| console.log('[HStacks] Request headers:', this.headers); |
Contributor
There was a problem hiding this comment.
Access token is logged in plaintext via headers logging; redact or remove to avoid credential leakage.
Prompt for AI agents
Address the following comment on packages/mcp-connectors/src/connectors/hstacks.ts at line 92:
<comment>Access token is logged in plaintext via headers logging; redact or remove to avoid credential leakage.</comment>
<file context>
@@ -0,0 +1,396 @@
+ }
+
+ try {
+ console.log('[HStacks] Request headers:', this.headers);
+ const response = await fetch(url, options);
+ console.log(`[HStacks] Response status: ${response.status} ${response.statusText}`);
</file context>
Suggested change
| console.log('[HStacks] Request headers:', this.headers); | |
| console.log('[HStacks] Request headers:', { ...this.headers, 'Access-Token': '***' }); |
| import { createMockConnectorContext } from '../__mocks__/context'; | ||
| import { HStacksConnectorConfig } from './hstacks'; | ||
|
|
||
| describe('#HStacksConnector', () => { |
Contributor
There was a problem hiding this comment.
Tests perform live HTTP calls without stubbing; add MSW-based request mocking like other connector specs to avoid flaky and external network-dependent tests.
Prompt for AI agents
Address the following comment on packages/mcp-connectors/src/connectors/hstacks.spec.ts at line 6:
<comment>Tests perform live HTTP calls without stubbing; add MSW-based request mocking like other connector specs to avoid flaky and external network-dependent tests.</comment>
<file context>
@@ -0,0 +1,215 @@
+import { createMockConnectorContext } from '../__mocks__/context';
+import { HStacksConnectorConfig } from './hstacks';
+
+describe('#HStacksConnector', () => {
+ describe('.GET_HSTACKS_SCHEMA', () => {
+ describe('when valid credentials are provided', () => {
</file context>
|
|
||
| ```bash | ||
| # Deploy a single Ubuntu server with nginx in Germany | ||
| bun start --connector hstacks --credentials '{"accessToken":"your-token-here"}' |
Contributor
There was a problem hiding this comment.
CLI example omits the required "-- --" before connector args; this will prevent options from reaching the server via turbo.
Prompt for AI agents
Address the following comment on docs/connectors/hstacks.md at line 73:
<comment>CLI example omits the required "-- --" before connector args; this will prevent options from reaching the server via turbo.</comment>
<file context>
@@ -0,0 +1,175 @@
+
+```bash
+# Deploy a single Ubuntu server with nginx in Germany
+bun start --connector hstacks --credentials '{"accessToken":"your-token-here"}'
+```
+
</file context>
Contributor
|
Hey Sean, would you let me have permissions to edit this branch. I need to remove the extra docs in order to merge this. All the docs for a connector should live in the tool descriptions. |
Author
|
@mattzcarey Sure thing! I'll be pushing up some cleaner code later today/early tomorrow. Best to wait until then, but I'll ping you with the access when it's ready :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's better than using IaC (Infrastructure as Code) to deploy infrastructure? Using LLMs to describe what kind of infrastructure you want and have the IaC generated, validated and deployed for you!
With the hstacks connector, and user can deploy any kind of cloud resource to Hetzner Cloud in seconds - going from zero, to 100s of Servers, Firewalls, and Elastic volumes in an instance (pun intended).
No more handcrafting your resources, let the MCP do it for you! 😎
Summary by cubic
Adds a new HStacks MCP connector to deploy and manage cloud infrastructure via hstacks.dev. Enables stack validation, deployment, status checks, and resource discovery with docs and tests.